Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81007 - make.conf.example encourages system-breaking changes to CHOST
Summary: make.conf.example encourages system-breaking changes to CHOST
Status: RESOLVED FIXED
Alias: None
Product: [OLD] Docs-user
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2005-02-06 11:02 UTC by Marty Rosenberg
Modified: 2005-07-14 06:58 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marty Rosenberg 2005-02-06 11:02:01 UTC 
The /mnt/gentoo/etc/make.conf.example file has a section called "Host setting" that explicitly states that the user should

# Change this line as appropriate (i686, i586, i486, or i386).
...
CHOST="i686-pc-linux-gnu"

It should be specified that only stage1 users should change the CHOST setting, and it should also be stated inside the make.conf.example that it is unsafe to change it otherwise.

Reproducible: Always
Steps to Reproduce:
N/A
Actual Results:  
N/A

Expected Results:  
# DO NOT CHANGE THIS SETTING UNLESS YOU ARE USING STAGE1!
Comment 1 Sven Vermeulen (RETIRED) gentoo-dev 2005-02-14 08:12:38 UTC 
Assigning to the portage peeps.

Note that the documentation (handbook) already has this warning.
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2005-02-15 06:44:35 UTC 
Added for all archs that have a choice about CHOST and didn't have a forbidding warning already.
Comment 3 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:38 UTC 
Fixed on or before 2.0.51.22-r1
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:26 UTC 
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.