this problem only seems to happen when ACCEPT_KEYWORDS="~x86" is selected, which means gcc-3.2.3 will be built. this doesn't happen when gcc-3.3 or gcc-3.2.2 is selected to be built in the bootstrap. when ~x86 is used, bootstrap.sh seems to build both the 'stable' pkg's and the 'unstable' pkg's together, then on the next emerge (such as emerge system) the older duplicate packages are then unmerged. it's very annoying, as the bootstrap takes 2x as long, and portage is just unmerging the excess builds right after anyway. Reproducible: Always Steps to Reproduce: 1. Set portage to compile gcc-3.2.3 during bootstrap (ACCEPT_KEYWORDS=~x86) 2. run /usr/portage/scripts/bootstrap.sh 3. watch the build take 2x longer than usual 4. watch the excess (older version builds of gcc, glibc, etc) become unmerged on the very next instance of emerge. Actual Results: bootstrap took 2x as long, and the next emerge unmerged the excess (older) builds. Expected Results: bootstrap should only have only built ~x86 packages not x86 *and* ~x86 ;). i.e. bootstrap should only build once, not make duplicates. athlon-xp 2600+ 333fsb 512mb pc2700
we do not support bootstrapping on ~arch KEYWORDS, so I'm rather tempted to close this as WONTFIX. However, if someone wants to fix the bootstrap.sh script, then that's fine too.
I will look @ the script
this will have to wait - we will not be supporting ~x86 bootstraps anytime soon
