Jay wrote on 08 September 2008 22:44:
> If you /really/ want to go through intermediate versions,
> then just remove -disable-bootstrap.
I'd highly recommend always building a full bootstrap, but of course it does
take longer.
> Or build twice, should be about the same thing:
I wouldn't rely on that myself.
> Without -disable-bootstrap, gcc gets built with the existing compiler
> (gcc 3.x in a typical Cygwin case, but the larger point is it could be
> not even gcc), and then uses itself to build itself.
>
> That it is able to build itself is some large measure of a passing test.
More than that: it builds itself, then uses the one it built to build itself
again, then compares that the two generate the exact same binaries (except
timestamps). That's a good indicator of consistency and that it's independent
of the host compiler altogether.
> Look at gcc -v for other suggested switches to configure.
> Such as the thread model. It seems to default to none instead of posix.
On the whole, it's as well not to use any configure switches that you don't
know for a fact are absolutely necessary. The default values should be sane
for the platform.
> But what I show above is an ok start.
You shouldn't need --disable-nls any more these days, I haven't had to use
it in quite a while.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
