This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Difficulty building gcc 4.3.2 under i386-pc-cygwin
- From: Jay <jay dot krell at cornell dot edu>
- To: <cygwin at cygwin dot com>, <tmacchant2 at yahoo dot co dot jp>, <wewo at smallwaters dot com>
- Date: Mon, 8 Sep 2008 21:43:37 +0000
- Subject: RE: Difficulty building gcc 4.3.2 under i386-pc-cygwin
- References: <1220909037.6401.ezmlm@cygwin.com>
You can build gcc 4.3.1 and 4.3.2 just fine from the existing Cygwin gcc 3.x package.
The error also /appeared/ to have the object directory under the source
directory. Don't do that.
I use roughly:
mkdir /obj/gcc.1
cd /obj/gcc.1
/src/gcc/configure -disable-nls -disable-bootstrap
make
it generally works.
There is no need to go through intermediate versions,
not in going from Cygwin's 3.x to current 4.3.x. (I'll try 4.4/trunk soon).
If you /really/ want to go through intermediate versions,
then just remove -disable-bootstrap.
Or build twice, should be about the same thing:
mkdir /obj/gcc.1
cd /obj/gcc.1
/src/gcc/configure -disable-nls -disable-bootstrap
make
make install
rm -rf *
/src/gcc/configure -disable-nls -disable-bootstrap
make
make install
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.
Look at gcc -v for other suggested switches to configure.
Such as the thread model. It seems to default to none instead of posix.
But what I show above is an ok start.
- Jay
--
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/