This is rather a complex test (Boost Python regression tests), but using the latest CURRENT OpenPKG with binutils 2.17 leads to errors like this:

    "g++" -L"/openpkg/lib/python2.4/config"  -o "/home/cae/boost-regression/RC_1_34_0/results/boost/bin.v2/libs/python/test/andreas_beyer.test/gcc-
4.1.1_sunos_i86pc/debug/debug-symbols-off/threading-multi/andreas_beyer_ext.so" -Wl,-h -Wl,andreas_beyer_ext.so -shared -Wl,--start-group "/home/cae/boost-regression/RC_1_34_0/results/boost/bin.v2/libs/python/test/andreas_beyer.test/gcc-
4.1.1_sunos_i86pc/debug/debug-symbols-off/threading-multi/andreas_beyer.o" "/home/cae/boost-regression/RC_1_34_0/results/boost/bin.v2/libs/python/build/gcc-4.1.1_sunos_i86pc/debug/debug-symbols-off/threading-multi/libboost_python-gcc41-mt-gd-1_34.so.1.34.0
"   -lpython2.4 -lrt -Wl,--end-group -Wl,--strip-all -pthreads 

/openpkg/bin/ld: /home/cae/boost-regression/RC_1_34_0/results/boost/bin.v2/libs/python/build/gcc-4.1.1_sunos_i86pc/debug/debug-symbols-off/threading-multi/libboost_python-gcc41-mt-gd-1_34.so.1.34.0: dlsym: invalid version 3 (max 0)
/home/cae/boost-regression/RC_1_34_0/results/boost/bin.v2/libs/python/build/gcc-4.1.1_sunos_i86pc/debug/debug-symbols-off/threading-multi/libboost_python-gcc41-mt-gd-1_34.so.1.34.0: could not read symbols: Bad value

collect2: ld returned 1 exit status
If you can't read those long lines they end with:
dlsym: invalid version 3 (max 0)
could not read symbols: Bad value

If I revert to the binutils 2.16.1 package from STABLE, the exact same command runs without error, without recompiling any of the objects.

Is this an OpenPKG bug or a binutils bug?  I'm guessing the latter.  In the meantime, I think it might be time for me to track the STABLE branch for a while :)

--
Caleb Epstein


Reply via email to