Bug#335486: [Pkg-openssl-devel] Bug#335486: openssl: FTBFS (ppc64): "gcc: '-b' must come at the start of the command line"

Andreas Jochens aj at andaco.de
Mon Oct 24 18:25:20 UTC 2005


Hello Kurt,

thanks for your quick reply to my report.

On 05-Oct-24 19:44, Kurt Roeckx wrote:
> Why does it fail?  What error message does it give?  I think you
> should look at getting that compiled instead of just removing it.

The build fails with the following error:

gcc -I. -I.. -I../include -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DB_ENDIAN -DTERMIO -O3 -g -Wall   -c -o o_dir.o o_dir.c
make[2]: *** No rule to make target `linux_ppc64.o', needed by `lib'.  Stop.
make[2]: Leaving directory `/srv/dbuild/tmp/openssl-0.9.8a/crypto'

It seems that linux_ppc64.o should be generated by the assembler from
linux_ppc64.s which in turn should be created by the perl script
crypto/bn/asm/ppc.pl. Somehow this does not work and I do not know
how to fix this.

However, I compiled openssl without the 'linux_ppc64.o' in the
'Configure' line and the resulting binary seems to work fine.

I guess that the assembler parts get replaced by default C routines
which should not be that bad. The crypto/bn/asm/README even says
that some of the assembler routines have been created using gcc output.

But I am no openssl expert at all and I may be wrong here.

Regards
Andreas Jochens




More information about the Pkg-openssl-devel mailing list