On Fri, 2007-12-21 at 01:32 +0000, Greg Chicares wrote:
> On 2007-12-20 23:22Z, kev c wrote:
> > --- Earnie Boyd <earnie@...> wrote:
> >> Quoting kev c <kevcormier@...>:
> >> > I am useing the build script now it is wonderful.
> >> > But I was wondering about the target spec why would
> >> > you want to use some thing like i686-pc-mingw32
> >> > instead of just i386-mingw32.
> >> Because the string has meaning. See autoconf
> >> documentation for more detail.
> > What exact meaning does the string have. The autoconf
> > documentation doesnt say much about it. It didnt
> > really answer my question.
> Then consult the autobook. I'm sure it explains each field
> in a configuration name.
The meaning is explained in the README file, which accompanies *our*
build script package; for convenience, it is:--
And yes, the pc *does* have meaning, as the VENDOR tag; however, it does
not have any *significant* meaning, and is therefore quite redundant.
That is why our build scripts default to omitting it, and naming the
cross-compiler suite as i386-mingw32-*. (I call mine i586-mingw32-*,
and many users will choose i686-mingw32-*). It is important that you
have at least a valid CPU tag, and the OSTYPE *must* be at least
mingw32, (many Linux distributors call it mingw32msvc, which IMO is
absolutely hideous, if not confusing, for to me it implies some
relationship to the Microsnot compiler, which just doesn't exist), but
the VENDOR tag serves no real purpose, and may be safely omitted.