I am trying to prepare a very compatible installation of gentoo (I am trying to identify a problem with my PC). I am using a no-problem PC to prepare the installation. I have CHOST="i386-pc-linux-gnu" CFLAGS="-O2 -pipe -march=i386" CXXFLAGS="${CFLAGS}" in my make.conf I started from stage1. However, after the bootstrap process the following behavior is observed. The new system is in /mnt/gentoo and the commands shown are not chrooted. root@yel root # /mnt/gentoo/sbin/ldconfig -v /lib: /usr/lib: /usr/local/lib: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2: /usr/lib/opengl/nvidia/lib: /usr/lib/mozilla: /usr/X11R6/lib: /opt/blackdown-jre-1.4.1/lib: /usr/lib/fltk-1.1: /opt/blackdown-jre-1.4.1/lib/i386: (hwcap: 0x1000000000000) root@yel root # /sbin/ldconfig -v /lib: libtermcap.so.2 -> libtermcap.so.2.0.8 libpam_misc.so.0 -> libpam_misc.so.0.75 .... and so on. The just-compiled ldconfig does not create any links and creates a 64 bytes long /etc/ld.so.cache (essentially empty). Only changing -march to i486 and running /usr/portage/scripts/bootstrap.sh 2 solves the problem. Maybe it is not a gentoo problem after all... I should be fine with -march=i486 only (I am thinking of running this on a VIA-C3 CPU) but I just wanted to go as ordinary as possible. I confirmed the bug on two different systems + a livecd installation inside vmware. Reproducible: Always Steps to Reproduce: 1. start a new gentoo installation from stage1 (doesn't matter if from a CD or a live system). 2. set -march=i386 in /etc/make.conf 3. run /usr/portage/scripts/bootstrap.sh 4. run "ldconfig -v" Actual Results: /etc/ld.so.cache was empty (64 bytes) and no links to libraries were created Expected Results: /etc/ld.so.cache should have had some contents + the appropriate library links should have been created
Stefan, seen anything like this on glibc-alpha lists ?
Haven't seen this before, looks intresting though, will try and reproduce the error here.
I should also note that gcc3 compiled for i386, cannot link objects against libstdc++ .... I will take a wild guess, and say it is prob related. Note that this has been an issue from 3.1 (not sure about 3.0.4 ...), and there might even be an open bug about it ... not sure.
It doesn't seem like anyone is actively trying to fix this. I don't think it affects many people and will affect even fewer people over time. I'm resolving this as WONTFIX. Martin, please reopen if neccessary.