Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <00ed01c1443d$7d0f19c0$40eb85ce@amr.corp.intel.com>
From: "Tim Prince" <tprince AT computer DOT org>
To: "Richard Chan" <chanricz AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <01C14408 DOT A0337AC0 AT MICRONSERVER>
Subject: Re: gcc 3.01 Build ??
Date: Sun, 23 Sep 2001 07:39:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

I thought it was up to 3.0.2.

You should be able to find useful information in the standard gcc
build information plus the archives of this list.  Minimum
configure parameters (useful for most of us)
are --with-included-gettext --enable-sjlj-exceptions .  Before
running configure, you should set the CFLAGS, CXXFLAGS to
combinations you consider suitable.  BOOT_CFLAGS is the most
important one during a bootstrap build.  CFLAGS must include -g,
if you wish to have -g available in all supported
anguages.  -march=pentiumpro -Os -pipe ought to be improvements
over the default build options.

I believe java will not build out of the box.

You might wish to build binutils with an increase in the ALIGN..
parameter in bfd/coff-i386.c, in order to get reasonable
performance with 64-bit data.  Configure parameters same as
above.  This is likely to break the standard cygwin g++ library,
which is not used by 3.0.x.  No need to rebuild binutils if you
don't care about performance.

If you install binutils in /usr/local (the default), your new gcc
build will default to the original; you would need to
configure --with-as=/usr/local/bin/as in order to use the new
one.  You can also do an integrated binutils/gcc build.  When you
install your new gcc to /usr/local, your new copy becomes the
default (contrary to normal gcc behavior).

If you wish to run the gcc testsuite, I believe that cygwin has
not yet accepted all needed patches to the .exp files.  I really
meant to make a diff between the working files and the ones which
come with cygwin, so I can quickly patch a new installation.
Maybe tomorrow.

----- Original Message -----
From: "Richard Chan" <chanricz AT yahoo DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, September 23, 2001 5:19 AM
Subject: gcc 3.01 Build ??


> Hi
>
> I understand that the latest release of cgywin binaries equips
with gcc
> 2.95.3.  If I want to try the gcc 3.0.1 and do my own
compliation, do u
> have any tips and guidelines to me ??  Thanks !
>
> Rgds,
> Richard



--
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/