Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41049 - CHOST specification in make.conf
Summary: CHOST specification in make.conf
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: John Davis (zhen) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-09 16:59 UTC by Evan Langlois
Modified: 2005-03-25 11:24 UTC (History)
0 users

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 Evan Langlois 2004-02-09 16:59:59 UTC
CHOST in the (minimal) make.conf file says i386, but the make.conf.sample says i686.  Its unclear as to which is correct, as it matters if you are building from stage3 and reinstall GCC!

Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.
Comment 1 Evan Langlois 2004-02-09 17:02:37 UTC
Oops - forgot to say, this is the gentoo-2004 stage3 tarball.
Dated 20040204.  Downloaded from:

http://www.gtlib.cc.gatech.edu/pub/gentoo/experimental/x86/stages/stage3-x86-20040204.tar.bz2

-- Taro
Comment 2 John Davis (zhen) (RETIRED) gentoo-dev 2004-02-10 12:33:20 UTC
actually, this is not a bug. Currently, the CHOST is set to whatever is defined in the arch's default settings. The default CHOST for regular x86 is in fact i386, so catalyst is doing what it is suppossed to do. If you take a gander at one of the p4, p3, or athlon-* stages, you will see that it is set correctly. If you have access to CVS, check out arch/x86.py in the catalyst source tree.

From x86.py:

class arch_x86(generic_x86):
        "builder class for generic x86 (386+)"
        def __init__(self,myspec):
                generic_x86.__init__(self,myspec)
                self.settings["CFLAGS"]="-O2 -mcpu=i686 -fomit-frame-pointer"
                self.settings["CHOST"]="i386-pc-linux-gnu"
Comment 3 Evan Langlois 2004-02-10 14:36:10 UTC
OK,

Technical discussions aside.

Which would average joe user actually set in make.conf?   A stage 3 has already has this set, and changing it causes problems - I had tons of problems with this issue because I was dumb enough to change it and think that re-emerging GCC would fix all places where the old CHOST setting was referenced (it doesn't).

So, if i386 is correct, fine.  Change make.conf.sample and document this accordingly.  Don't give it both ways and expect the user to figure out which one the compiler tools were originally set to use.

Comment 4 John Davis (zhen) (RETIRED) gentoo-dev 2004-02-11 13:20:04 UTC
Joe user would also download the correct stage for his arch as defined by the handbook. Since these are testing stages, I did not bother to build the optimized versions of them. The only reason that Joe User would use a x86 stage is if he had a lower speed box to use them on. This is a one of those issues where the user *has* to read the documentation - we create different stages with different CHOSTs for a reason.
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2005-03-25 11:24:24 UTC
Moving these so we can remove the "Install CD" component from "Gentoo Linux".

I apologize to everyone for this spam, but according to the bugzilla developers,
this is the only reasonable way to do this.