I was installing gentoo on a server from stage1. script/boostrap.sh stopped when configuring libart_lgpl. Then I did a script/bootstrap.sh -f to fetch all packages, I discovered then that libart_lgpl was wanted by gcc-3.4.2-r2. I read gcc ebuild and discovered that libart_lgpl was needed for gcj. I had gcj in my USE flag in make.conf, but script/bootstrap.sh hasn't set 'build' USE flag to avoid request of libart_lgpl. It is supposed to do so, but it didn't worked that way. I read bootstrap.sh and found line 206 export USE="${ORIGUSE} bootstrap" [...] and then on line 239 emerge ${STRAP_EMERGE_OPTS} ${myGCC} || cleanup 1 while before line 206 USE variable contains build flag line 206 strips it away. but emerge gcc is supposed to use 'build' flag. I think line 206 mustexport be changed in export USE="${ORIGUSE} bootstrap build" Well, I told the bug. I will attach make.conf I wrote. I think my bugfix should work. I use that bugfix to complete boostrap and now I'm happy :-) Bye
Created attachment 40871 [details] make conf used in installing
Created attachment 40872 [details, diff] what I did to have script/bootstrap.sh working
doh, just a few typos...
You set ACCEPT_KEYWORDS="~x86" in your make.conf. This is not supported because of the error you just experienced and other potential errors that might come up. We cannot guarantee a flawless installation with ~arch set.
This same error occurs w/o using ~arch. I am using x86 (stable) and can't install emerge system.
Created attachment 50423 [details] output of bootstrap.sh --info have seen the same error while bootstrapping, w/o ACCEPT_KEYWORD="~arch". The error is also described in bug 76415. The error message is: checking for i686-pc-linux-gnu-g++... g++ checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/libart_lgpl-2.3.16/work/libart_lgpl-2.3.16/config.log The output of bootstrap.sh --info is attached. The problem can be solved by dropping the gcj use flag, or exporting STAGE1_USE=build before bootstrapping.
Looking into this.
Chris: Have had time to look into this? This problem still happens for me (on ppc64).
Actually, we're replacing the bootstrap script with a new one once 2005.0 is out, so this won't be valid any longer. For now, you could use the bootstrap-new.sh script along with "emerge -e system" to build a system.
nice! I'll definetly try that out! :-)
new bootstrap.sh fixed this problem.
I figured it would have...
