During the upgrade on two different Opteron based systems, the following occured in the same place during the imlib2 upgrade - /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.4/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.4/../../../../lib64/libz.a(inflate.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.4/../../../../lib64/libz.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [libImlib2.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/imlib2-1.1.1/work/imlib2-1.1.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/imlib2-1.1.1/work/imlib2-1.1.1' make: *** [all-recursive-am] Error 2 Reproducible: Always Steps to Reproduce: 1.emerge sync 2. emerge -uDpv world 3. Will post tomorrow when I have access to the systems.
hmm... the current stable imlib2 is 1.1.2 btw. also, have you tried to sync up and re-emerge zlib? there was a bug that i fixed that would prevent libz.so from being built sometimes. it seems you've been snagged by that, since imlib2 should be using that instead of libz.a...
re-emerging zlib worked on both systems. imlib2 emerged fine after zlib was re-emerged. Bob
*** This bug has been marked as a duplicate of 61868 ***
