As mentionned in the Summary, I had an issue compiling x11-libs/gdk-pixbuf-2.26.4 on an AMD64-based system, doing the equivalent of a stage1 in a chroot by launching an "emerge -Neuv world". gdk-pixbuf would block without fail, until I read on the internet a couple of times that their build system did not like parallel building; my make.conf currently defines MAKEOPTS as "-j8", as I have a fairly recent Core i7 and 16gb of RAM. After a couple of hours, I had the glorious idea of launching the build for gdk-pixbuf only this way: MAKEOPTS="-j1" emerge gdk-pixbuf And instead of complaining like so: libtool: install: /usr/lib64/portage/bin/ebuild-helpers/xattr/install -c .libs/libgdk_pixbuf-2.0.so.0.2600.4 /var/tmp/portage/x11-libs/gdk-pixbuf-2.26.4/image//usr/lib64/libgdk_pixbuf-2.0.so.0.2600.4 libtool: install: warning: relinking `libpixbufloader-png.la' libtool: install: (cd /var/tmp/portage/x11-libs/gdk-pixbuf-2.26.4/work/gdk-pixbuf-2.26.4/gdk-pixbuf; /bin/sh /var/tmp/portage/x11-libs/gdk-pixbuf-2.26.4/work/gdk-pixbuf-2.26.4/libtool --silent --tag CC --mode=relink x86_64-pc-linux-gnu-gcc -std=gnu99 -march=corei7 -O2 -pipe -Wall -avoid-version -module -Wl,-O1 -Wl,--as-needed -o libpixbufloader-png.la -rpath /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders io-png.lo -lpng15 libgdk_pixbuf-2.0.la -lgmodule-2.0 -pthread -lrt -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lpng15 -lm -inst-prefix-dir /var/tmp/portage/x11-libs/gdk-pixbuf-2.26.4/image/) /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lgdk_pixbuf-2.0 collect2: ld returned 1 exit status , it passed right through. Once again, the solution was to force MAKEOPTS="-j1".
Created attachment 358680 [details] Build Log
(In reply to Renaud from comment #0) > Once again, the solution was to force MAKEOPTS="-j1". That's a workaround, not a "solution". *** This bug has been marked as a duplicate of bug 484962 ***
