Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dockeen" <dockeen AT mchsi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Re: What's wrong? gcc brain-damaged on cygwin?
Date: Sun, 22 Dec 2002 10:18:51 -0600
Message-ID: <NCBBLKKJGBJOLDFMCKFPMECFCBAA.dockeen@mchsi.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

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
bootstrap
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
the
devel category works really well.  If for some reason you want to do
something
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.

Wayne

p.s. Don't try this at home, because there are details of how I set up my
build
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
--enable-languages=c,c++,f77 --enable-sjlj-exceptions

I also seem to recall using a -k option to skip over some gcj issues.  It
worked,
but it took some time to figure out...



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/