If I change CFLAGS in /etc/make.conf, it would be best to rebuild the world with "emerge -e world". It needs to be explained somewhere in the handbook that changes to /etc/make.conf do NOT automatically cause a rebuild of the world when CFLAGS is changed, as apparently portage does not clue into changes to /etc/make.conf as a file dependency and does not therefore rebuild the world when CFLAGS value has changed. User scenario: 1. User initially sets CFLAGS to include -march=VALUE1 2. User builds a new system using the installation guide 3. User gets deep into the installation guide and finds some flag that needs to be set for specific architectures such as omiting frame pointers or changes to -march=VALUE2 4. User makes that change and runs emerge and finds that not all packages are rebuilt. Therefore, perhaps a sentence or two is in order to be added to the handbook in the sections (that's plural) that explain when to use the -e switch w.r.t. changes to CFLAGS? -bg
Not in the handbook. Users do not need to mess about re-emerging world when installing. You don't normally need to recompile your entire world right then and there just because you change a few CFLAGs. You can just gradually rebuild everything with each merge after the change. If you change CHOST, *then* you need to rebuild world, and we have a guide for that: http://www.gentoo.org/doc/en/change-chost.xml Or if you upgrade to a new major version of your compiler: http://www.gentoo.org/doc/en/gcc-upgrading.xml Or if you're using a stage1 or stage2 tarball: http://www.gentoo.org/doc/en/faq.xml#stage12
