This is the mail archive of the
mailing list for the Cygwin project.
Re: What's wrong? gcc brain-damaged on cygwin?
- From: "Dockeen" <dockeen at mchsi dot com>
- To: <cygwin at cygwin dot com>
- Date: Sun, 22 Dec 2002 10:18:51 -0600
- Subject: Re: What's wrong? gcc brain-damaged on cygwin?
When I built my own, I built it with C,C++ and f77 enabled. The configure
(I had a number of options added, it was not just ./configure) and the make
part of the process took an hour on P4 type machines, 10 hours on this old
P2. (make install was quick).
But back to the fundamental point. The gcc compiler suite (C,C++,f77) from
devel category works really well. If for some reason you want to do
like try to build and play with gcc-3.3, then put it in a parallel directory
structure - use prefix in your configure, it makes a LOT more sense.
p.s. Don't try this at home, because there are details of how I set up my
directory that play into this, but this is an example of what my configure
command looked like:
srcdir/configure --prefix=/mygcc --enable-threads=win32 --with-system-zlib
I also seem to recall using a -k option to skip over some gcj issues. It
but it took some time to figure out...
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html