When emerging openct I get the following error: /bin/sh ../../libtool --mode=link x86_64-pc-linux-gnu-gcc -Wall -fno-strict-ali asing -O2 -march=k8 -pipe -L/usr//lib -o opensc-signer.la -rpath /usr/lib64/o pensc -module -avoid-version opensc_signer_la-opensc-crypto.lo opensc_signer_la- opensc-support.lo opensc_signer_la-signer.lo opensc_signer_la-stubs.lo opensc_si gner_la-dialog.lo ../../src/libopensc/libopensc.la -lcrypto -lassuan -lpthread x86_64-pc-linux-gnu-gcc -shared .libs/opensc_signer_la-opensc-crypto.o .libs/op ensc_signer_la-opensc-support.o .libs/opensc_signer_la-signer.o .libs/opensc_sig ner_la-stubs.o .libs/opensc_signer_la-dialog.o -Wl,--rpath -Wl,/var/tmp/portage /opensc-0.9.4/work/opensc-0.9.4/src/libopensc/.libs -L/usr//lib ../../src/libope nsc/.libs/libopensc.so -lcrypto -lassuan -lpthread -march=k8 -Wl,-soname -Wl,op ensc-signer.so -o .libs/opensc-signer.so /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/../../../../x86_64-pc-linux-gnu/bin/ld: / usr//lib/libassuan.a(assuan-errors.o): relocation R_X86_64_32 against `a local s ymbol' can not be used when making a shared object; recompile with -fPIC /usr//lib/libassuan.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[4]: *** [opensc-signer.la] Error 1 make[4]: Leaving directory `/var/tmp/portage/opensc-0.9.4/work/opensc-0.9.4/src/ signer' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/opensc-0.9.4/work/opensc-0.9.4/src/ signer' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/opensc-0.9.4/work/opensc-0.9.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/opensc-0.9.4/work/opensc-0.9.4' make: *** [all] Error 2 !!! ERROR: dev-libs/opensc-0.9.4 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile opensc-0.9.4.ebuild, line 49: Called die dev-libs/opensc-0.10.1 does not have this problem - maybe it should be marked stable to fix this bug
(In reply to comment #0) > dev-libs/opensc-0.10.1 does not have this problem - maybe it should be marked > stable to fix this bug > Good idea... :)
amd64 stable
hppa stable
Alpha done.
