View previous topic :: View next topic |
Author |
Message |
farrenheit n00b
Joined: 20 Jun 2010 Posts: 29
|
Posted: Sun Jun 20, 2010 1:03 pm Post subject: list of all possible CHOST values, non-ambiguous description |
|
|
I am a newcomer to Gentoo, wanted the extreme performance and customization advertised.
I have followed the stage1 installation instructions and am now at the bottom of section 5: Installing the Gentoo Installation Files.
I am at the part where it talks about configuring /etc/make.conf, and not proceeding until I have a make.conf that I feel fits me. I'm stuck because I can't find a list of all valid CHOST values.
I've read man pages for portage's make.conf, and I've read it said that the Gentoo Handbook has a list of all CHOST values, but I can't find that list. I look in the gcc handbook for target machine types, and they don't have any values like:
CHOST="i686-pc-linux-gnu"
instead, they only have values like: i386, i486, i586, i686, pentium, pentium-mmx, pentiumpro, pentium2, pentium3, pentium4, k6, k6-2, k6-3, athlon, athlon-tbird, athlon-4, athlon-xp and athlon-mp. They don't have any cpu values mixed with "pc" or "linux" or "gnu" in there, so I don't know if I can just put random words into the CHOST as I wish, like:
CHOST="amd64-pc-core2-quadcore-linux-gentoo-whatever"? |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Sun Jun 20, 2010 1:17 pm Post subject: |
|
|
CHOST has to match your architecture, you can't make up custom CHOST's.
i686-pc-linux-gnu for 32-bit Intel
x86_64-pc-linux-gnu for 64-bit |
|
Back to top |
|
|
farrenheit n00b
Joined: 20 Jun 2010 Posts: 29
|
Posted: Sun Jun 20, 2010 1:24 pm Post subject: |
|
|
thank you. so, other than these 2 options, there are no more for CHOST? |
|
Back to top |
|
|
farrenheit n00b
Joined: 20 Jun 2010 Posts: 29
|
Posted: Sun Jun 20, 2010 1:32 pm Post subject: |
|
|
i think i understand better now:
so CHOST is not really a value to be set by user so much as it will be set automatically later in the installation, and should only be changed in unusual circumstances. |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Sun Jun 20, 2010 1:32 pm Post subject: |
|
|
Jaglover wrote: |
i686-pc-linux-gnu for 32-bit x86
x86_64-pc-linux-gnu for 64-bit x86_64 |
ia64-unknown-linux-gnu for 64-bit ia64... |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Sun Jun 20, 2010 1:41 pm Post subject: |
|
|
CHOST depend on what your cpu can do.
some cpu can use multi CHOST, but one or two generally are the best for your cpu.
for example a core2 cpu could use: i486-pc-linux-gnu, i586-pc-linux-gnu, i686-pc-linux-gnu and x86_64-pc-linux-gnu
but i would say, it you just fail to pickup the right livecd to boot, well, easy, your livecd won't boot, so you can't really do that.
and if you pickup a livecd that your cpu can boot, you've find one your cpu could handle.
and so, just emerge --info and look how the livecd set the CHOST, and reuse it.
if for example you pickup the x86 livecd and your chost show i686-pc-linux-gnu where you want to use 64bits then you will need the x86_64 (amd64) livecd to get it.
So, pickup the right livecd and don't care about your CHOST, just emerge --info from the livecd and use that one (and i suppose the default make.conf from the livecd might already have this set right for you). |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21706
|
Posted: Sun Jun 20, 2010 3:57 pm Post subject: Re: list of all possible CHOST values, non-ambiguous descrip |
|
|
farrenheit wrote: | instead, they only have values like: i386, i486, i586, i686, pentium, pentium-mmx, pentiumpro, pentium2, pentium3, pentium4, k6, k6-2, k6-3, athlon, athlon-tbird, athlon-4, athlon-xp and athlon-mp. | These are values that can be listed in the -march= and -mtune= lines to fine tune the generated code to run better on, or only on, specific CPUs. Not all architectures are valid for all CHOSTs. If you use an incompatible arrangement, gcc should fail to compile the code. You can then pick a more suitable value. Beware that you can set a -march= that instructs gcc to generate code that your CPU cannot run. This can be useful in some limited circumstances, but is probably not what you want for a new standalone system. |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Sun Jun 20, 2010 9:30 pm Post subject: |
|
|
krinn wrote: | Jaglover wrote: |
i686-pc-linux-gnu for 32-bit x86
x86_64-pc-linux-gnu for 64-bit x86_64 |
ia64-unknown-linux-gnu for 64-bit ia64... |
If you run Itanium you won't ask this question. |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9538 Location: beyond the rim
|
Posted: Sun Jun 20, 2010 10:35 pm Post subject: |
|
|
Just don't set CHOST in make.conf at all, rely on the profile to set the right value. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|