Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 140348 - Gentoo Handbook versus x86 Quick Install Guide
Summary: Gentoo Handbook versus x86 Quick Install Guide
Status: RESOLVED FIXED
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Installation Handbook (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: nm (RETIRED)
URL:
Whiteboard:
Keywords:
: 140355 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-07-14 05:12 UTC by Marc Blumentritt
Modified: 2006-08-30 18:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Blumentritt 2006-07-14 05:12:44 UTC
Hi,

in the x86 Quick Install Guide [1]  it is stated under "Code
Listing 2.38: Last edit of make.conf":
--snip--
You might want to recompile your whole system twice to make full use of
your latest configuration changes. It would take quite a long time to
complete and yield minimal speed benefits. It is recommended that you
let your system optimise itself gradually over time when new versions of
packages are released.
--end of snip--

Two remarks:
1.) The phrase "recompile your whole system twice" implicates (at least
for me) "emerge -e system && emerge -e system", while I read on the dev
list about the stage1-discussion [2], that it is recommend to do "emerge
-e world && emerge -e world && emerge --depclean", when you change your
compile options (well yes, and USE flags).

2.) In chapter "5.e. Configuring the Compile Options" [3] of the
Handbook there is nothing written comparing to this.


In the next Code Listing "Code Listing 2.39: Update your packages" of
the x86 Quick Install Guide there are some recommendations, what you
should, when you update your system:
--snip--
[...]
emerge libtool
[...]
etc-update
[...]
perl-cleaner all
[...]
python-updater
[...]
--end of snip--

Again you can find nothing about these recommendations in the handbook
in chapter "1.c. Maintaining Software" [4]. On the other hand you find
there the advise to run "emerge --depclean" and revdep-rebuild" after an
update of your complete system.


Both topics touch stuff, which is (in my opinion) crucial for Gentoo: changing compile options (which includes updates of toolchain packages in my opinion) and maintaining your system via world updates (which could change the toolchain). More informations about this and some good practicing advices in the handbook would be great!

Regards,
Marc


[1]http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml
[2]http://article.gmane.org/gmane.linux.gentoo.devel/33290/match=decision+remove+stage1+2+installation+documentation
[3]http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5#doc_chap5
[4]http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3
Comment 1 Łukasz Damentko (RETIRED) gentoo-dev 2006-07-14 05:44:47 UTC
*** Bug 140355 has been marked as a duplicate of this bug. ***
Comment 2 Marc Blumentritt 2006-07-26 09:14:05 UTC
Hi,

the code listing 2.38 in the x86 Quick Install Guide lists this code:
--snip--
Code Listing 2.38: Last edit of make.conf

mybox etc # nano -w make.conf
(Set -march to your CPU type in CFLAGS)
CFLAGS="-O2 -march=athlon-xp -pipe"
(Add the following line)
FEATURES="parallel-fetch ccache"
(Only add the following if you know what you're doing)
ACCEPT_KEYWORDS="~x86"
--end of snip--

The CFLAGS option "-march=athlon-xp" is marked blue for special attention. The change of the CFLAGS is what I was trying to point at with this bug. The Gentoo Handbook says nothing about "to recompile your whole system twice to make full use" of the CFLAGS change. This comment about recompilation is not about ACCEPT_KEYWORDS="~x86", because moving to testing is more or less only an upgrade of your packages (of course there are special packages like gcc to care about).

I just wanted to clarify this.

Regards,
Marc
Comment 3 nm (RETIRED) gentoo-dev 2006-08-30 18:42:16 UTC
Okay, I added a bit of information on why rebuilding is still a valid option, with a link pointing to the gcc upgrading guide for a more thorough discussion of rebuilding.

Also updated some package names in light of 2006.1's release. Thanks for reporting.