On a stage1-x86-2007.0 install using baselayout-vserver, "emerge -e system" fails for package dev-libs/gmp-4.2.2 because libtool gets confused over / cannot find libgmpxx.so.4.0.2. I am under the impression that, while this bug seems to be "invisible" for a normal stage3 install, it is still a bug in the ebuild, and filed this bug report as suggested by HTS (see forum URL). Reproducible: Always Steps to Reproduce: 1. Install Gentoo Installation Files as per handbook and chroot 2. ln -snf /usr/portage/profiles/default-linux/x86/vserver /etc/make.conf 3. emerge --unmerge baselayout 4. USE="build" emerge --oneshot baselayout-vserver 5. /usr/portage/scripts/bootstrap.sh 6. emerge -e system Actual Results: From gmp-4.2.2 emerge log: libtool: install: warning: remember to run `libtool --finish /usr/lib' /bin/sh ./libtool --mode=install /bin/install -c 'libgmpxx.la' '/var/tmp/portage/dev-libs/gmp-4.2.2/image//usr/lib/libgmpxx.la' libtool: install: warning: relinking 'libgmpxx.la' (cd /var/tmp/portage/dev-libs/gmp-4.2.2/work/gmp-4.2.2; /bin/sh ./libtool --mode=relink i686-pc-linux-gnu-g++ -Os -mtune=pentium4 -pipe -fomit-frame-pointer -o libgmpxx.la -rpath /usr/lib -version-info 4:2:0 dummy.lo cxx/isfuns.lo cxx/ismpf.lo cxx/ismpz.lo cxx/ismpznw.lo cxx/osdoprnti.lo cxx/osfuns.lo cxx/osmpf.lo cxx/osmpq.lo libgmp.la -inst-prefix-dir /var/tmp/portage/dev-libs/gmp-4.2.2/image/) mv: cannot stat `libgmpxx.so.4.0.2': No such file or directory libtool: install: error: relink ' libgmpxx.la' with the above command before installing it Emerging gmp with USE="nocxx" avoids the bug, but isn't a viable workaround really.
emerge --info please...
as well as the full build log
Created attachment 141668 [details] Output of emerge --info
Created attachment 141670 [details] Build log
Info attached as requested.
Ah... stupid. After masking gmp-4.2.2, and trying gmp-4.2.1-r1 (which failed, too), I diff'ed the log against one from an older vServer that worked. I stumpled over this: ... checking whether we are using the GNU C++ compiler... no <-- "no"? checking whether i686-pc-linux-gnu-g++ accepts -g... yes checking C++ compiler i686-pc-linux-gnu-g++ ${CFLAGS}... yes <-- "${CFLAGS}"? ... It turned out that, in make.conf, I wrote: ... CXXFLAGS="\${CFLAGS}" ... Note the backslash. This broke C++ compilation, unfortunately in a rather subtle way. Sorry for the hassle.
