Apparently, though unproven, at 16:42 on Friday 10 June 2011, Pandu Poluan did 
opine thusly:

> On Fri, Jun 10, 2011 at 05:46, walt <w41...@gmail.com> wrote:
> > On 06/08/2011 10:54 PM, Pandu Poluan wrote:
> >>   $ ./configure --prefix=/usr --build=x86-pc-linux-gnu
> > 
> > Hm.  That should be --build=i686-pc-linux-gnu (for 32-bit machines)
> > 
> > My first thought would be to grep through /etc/* for x86.  At this
> > minute I don't have a second thought :(
> 
> Amazing! You're right!
> 
> Apparently I created a make.conf with x86-pc-linux-gnu instead of
> i686-linux-gnu.
> 
> I'll blame that to installing too many x86_64-pc-linux-gnu systems :-P
> 
> ( That said, isn't it ... inconsistent that the flags are ~amd64 and
> ~x86 while the CHOST can be x86_64 and i686 ... )

Not at all inconsistent. Stupid, but not inconsistent.

AMD developed the 64 bit instructions set so it is correctly amd64. Intel 
developed the 32 bit instruction set so they can call it what they want it to 
be, which is x86.

Now, as for CHOST. Well, that comes from Red Hat who are deeply involved in 
glibc and gcc and they insist that the OneAndOnlyTrueName(tm) is x86_64.

Red Hat are flat out wrong of course, but that doesn't stop them punting their 
wrong idea and shoving it into the toolchain when we regular schmucks have to 
deal with it.

So now you know. The stupid ones are very very consistent in their stupidity.


-- 
alan dot mckinnon at gmail dot com

Reply via email to