When doing a stage1 install, after running bootstrap.sh, immediately running "emerge portage" fails with [Could not run/locate "i386-pc-linux-gnu- gcc"] Reproducible: Always Steps to Reproduce: 1. Start stage1 install 2. Run bootstrap.sh 3. run "emerge portage" Actual Results: portage fails to install with [Could not run/locate "i386-pc-linux-gnu-gcc"] Expected Results: portage to install and not fail I was able to "fix" this by running "emerge --nodeps --oneshot python" before doing "emerge portage." I think a better solution, though, would be to simply have python updated as a part of bootstrap.sh
1. There's no need to change CHOST besides cosmetics. 2. Please follow the handbook carefully when installing - you need to run "emerge --emptytree system" after bootstrapping. *** This bug has been marked as a duplicate of 88777 ***
Not true. Try using nptl with CHOST=i386-pc-linux-gnu. It won't work because of the ebuild requirements. Since I wanted nptl-support, it was absolutely neccesary to change CHOST.
It seems I am wrong; the above comment was based on old information. Apparently, the glibc + nptl only being on >i386 was fixed.