-----BEGIN PGP SIGNED MESSAGE-----


istari-[crypt/ssleay/crypto/bn] mcr 401 >uname -a
NetBSD istari.sandelman.ottawa.on.ca 1.2G NetBSD 1.2G (SSW) #2: Sat Oct  4 00:21:22 EDT 1997     mcr@istari.sandelman.ottawa.on.ca:/j/netbsd/src/sys/arch/i386/compile/SSW i386

SSLeay 0.8.1 19-Jul-1997

  In crypto/bn, the Makefile does:

(cd ../..; make -f Makefile.ssl DIRS=crypto SDIRS=bn sub_all)
making crypto...
making all in bn...
gcc  -c asm/x86-lnxa.s
ar r ../../libcrypto.a bn_add.o bn_div.o bn_exp.o bn_lib.o bn_mod.o bn_mul.o  bn_print.o bn_rand.o bn_shift.o bn_sub.o bn_word.o  bn_gcd.o bn_prime.o bn_err.o bn_sqr.o asm/x86-lnxa.o bn_recp.o bn_mont.o
ar: asm/x86-lnxa.o: No such file or directory
*** Error code 1

  The problem is that the default (/usr/share/mk/sys.mk) target for
.s.o is used.
  gcc -c asm/x86-lnxa.s leaves the .o file in the current directory. 

  SSLeay must be assuming that the default rule adds a -o.  Doing so
in all of NetBSD would break obj directories.

  But, the default rules are being used so that a higher level
Makefile can specify which code to include, and let the default rules
compile it (whether C or .o)

  Interim fix:
	ln -s ../x86-lnxa.o asm

  I think SSLeay is at fault here. Opinions?

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |
 Personal: mcr@sandelman.ottawa.on.ca. PGP key available.
 Corporate: sales@sandelman.ottawa.on.ca. 


  


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNEOVmKZpLyXYhL+BAQFL/QL8DqXCCxn+anH0t0Omycw64Sk3TvcC2hGo
QzZmzne74pZKcUXGhPxlgWo+6QB91fyMFO1agYwh/XLWqcB7vXkTUS+VOQIT5rMP
1yws7pYKI/uQwBiu3blyDq04wOMW8wTO
=VzLh
-----END PGP SIGNATURE-----