> There's just noe thing I'm not completely sure of. IIRC, gcc uses GNU
> as in the end stage of the compilation,
not necessarily! it can as well use bundled as.
> so one might wonder what that
> kind of fiddling with the PATH will actually do to gcc.
here is how it finds the way:
access("/usr/pd/gnu/lib/gcc-lib/sparc-sun-solaris2/egcs-2.91.66/as", 1) Err#2 ENOENT
access("/usr/pd/gnu/lib/gcc-lib/sparc-sun-solaris2/as", 1) Err#2 ENOENT
access("/usr/lib/gcc/sparc-sun-solaris2/egcs-2.91.66/as", 1) Err#2 ENOENT
access("/usr/lib/gcc/sparc-sun-solaris2/as", 1) Err#2 ENOENT
access("/usr/pd/gnu/sparc-sun-solaris2/bin/sparc-sun-solaris2/egcs-2.91.66/as", 1)
Err#2 ENOENT
access("/usr/pd/gnu/sparc-sun-solaris2/bin/as", 1) Err#2 ENOENT
access("/usr/ccs/bin/sparc-sun-solaris2/egcs-2.91.66/as", 1) Err#2 ENOENT
access("/usr/ccs/bin/as", 1) = 0
which doesn't look like having anything to do with PATH.
as for the problem itself. there is a special rule in
crypto/bn/Makefile.ssl which handles compilation of the module
in question:
asm/sparcv8plus-gcc.o: asm/sparcv8plus.S
gcc -E asm/sparcv8plus.S | as -xarch=v8plus /dev/fd/0 -o asm/sparcv8plus-gcc.o
Just modify it as following:
asm/sparcv8plus-gcc.o: asm/sparcv8plus.S
gcc -E asm/sparcv8plus.S | /usr/ccs/bin/as -xarch=v8plus /dev/fd/0 -o
asm/sparcv8plus-gcc.o
and you're set.
Andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
