Re: [vsipl++] [patch] Config update

[Jules Bergmann <jules@xxxxxxxxxxxxxxxx>]

Brooks,

> > >   - use GNU triplets (i686-pc-linux-gnu, powerpc-linux-gnu, powerpc-mcoe,
> > >     etc)
> > Note that powerpc-linux-gnu is not in fact a triplet; linux-gnu is a
> > single item.  It should be powerpc-unknown-linux-gnu, or have something
> > specific in place of the "unknown" for the system type.
> >
> > Similarly, powerpc-mcoe should be powerpc-unknown-mcoe or
> > powerpc-mercury-mcoe (if mcoe only runs on Mercury systems) or somesuch
> > to be a true triplet.
> I don't know if this is important for our purposes or not.  It might be,
> if we ever use something that expects to split the triplets into their
> component parts, but otherwise probably isn't....  (For one example, I
> suspect that autoconf's cross-compiler handling may expect triplets.)
The goal is consistency with Sourcery G++.  If that means sprinkling in 
"unknown"s, that's the way it is I suppose :)
> As an addendum -- for Cell, we settled on powerpc-cell-linux-gnu for the
> canonical triplet when documenting the --host option; I think it would
> be good to have this agree with that.
Sounds fine to me.  To be sure I understand the triplet format, 
shouldn't this be 'powerpc-cell-unknown-linux-gnu'?  Cell is an 
architectural variant of power, not a systems vendor, right?
				-- Jules

--
Jules Bergmann
CodeSourcery
jules@xxxxxxxxxxxxxxxx
(650) 331-3385 x705