This section contains this note: Note: A commented listing of all possible variables can be found in /mnt/gentoo/etc/make.conf.example. For a successful Gentoo installation you'll only need to set the variables which are mentioned beneath. It looks like it's saying that the minimum amount of work you need to do in /etc/make.conf is to set CFLAGS, CXXFLAGS, and MAKEOPTS, and that there is no maximum amount of work (i.e. you could configure anything mentioned in /etc/make.conf.example, but you don't need to do all that right away). In fact, after going through several install attempts, it looks like configuring more than CFLAGS, CXXFLAGS, and MAKEOPTS can actually cause install failures. E.G. setting PORTAGE_ELOG_SYSTEM="mail_summary" causes the next thing you emerge to fail with: !!! An error occured while trying to send logmail: (553, '5.5.4 <portage>... Domain name required for sender address portage', 'portage') Therefore, I suggest either changing the note to tell people to only set the variables mentioned and not set any others, or (preferably) continuing to allow the user to set other things, but listing settings which should not be set at this time. Things suggested for such a "don't set this now" list: - PORTAGE_ELOG_SYSTEM values "mail" or "mail-summary" because the host and domain name have not been configured for the system, yet. - setting (some? any?) USE flags appears to cause the initial emerge --sync to think that portage needs to be upgraded, which then fails because it thinks that /usr/lib/libgpg-error.a is in /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../..//.libs/libgpg-error.a . Reproducible: Always Steps to Reproduce: 1.See above 2. 3. Actual Results: Errors emerging portage or gentoo-sources or whatever is emerged next. Expected Results: Things are successfully emerged as directed by /etc/make.conf
(In reply to comment #0) > It looks like it's saying that the minimum amount of work you need to do in > /etc/make.conf is to set CFLAGS, CXXFLAGS, and MAKEOPTS, Actually you don't have to set them, there are sane defaults in that file. > and that there is no > maximum amount of work (i.e. you could configure anything mentioned in > /etc/make.conf.example, but you don't need to do all that right away). Correct. > In fact, after going through several install attempts, it looks like > configuring more than CFLAGS, CXXFLAGS, and MAKEOPTS can actually cause install > failures. Well, I see your point, but on the other hand, you can screw up pretty badly even with any of the three variables you've mentioned. > E.G. setting PORTAGE_ELOG_SYSTEM="mail_summary" causes the next > thing you emerge to fail with: > > !!! An error occured while trying to send logmail: > (553, '5.5.4 <portage>... Domain name required for sender address portage', > 'portage') Perhaps we should add a note to the make.conf.example saying that you have to configure your MSA prior to using any mail features of portage. Portage folks, comments? > - setting (some? any?) USE flags appears to cause the initial emerge --sync > to think that portage needs to be upgraded, Which doesn't harm. > which then fails because it thinks > that /usr/lib/libgpg-error.a is in > /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../..//.libs/libgpg-error.a . Another bug, please. If it doesn't work and you have followed the handbook and didn't screw up by some manual tweak, it should be fixed.
(In reply to comment #1) > (In reply to comment #0) > > E.G. setting PORTAGE_ELOG_SYSTEM="mail_summary" causes the next > > thing you emerge to fail with: > > > > !!! An error occured while trying to send logmail: > > (553, '5.5.4 <portage>... Domain name required for sender address portage', > > 'portage') > > Perhaps we should add a note to the make.conf.example saying that you have to > configure your MSA prior to using any mail features of portage. Portage folks, > comments? That looks like bug 150443.
OK, closing per previous comments.
