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
Message-Id: <200309151323.h8FDNqaA187168@pimout4-ext.prodigy.net>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Tim Prince <timothyprince AT sbcglobal DOT net>
Reply-To: tprince AT computer DOT org
To: tprince AT computer DOT org, John D Rogers <jrogers AT TheWorld DOT com>
Subject: Re: Rebuilding gcc 3.3.1 under cygwin?
Date: Mon, 15 Sep 2003 06:23:51 -0700
Cc: cygwin AT cygwin DOT com
References: <200309141811 DOT OAA17245285 AT shell DOT TheWorld DOT com> <200309150249 DOT WAA17196114 AT shell DOT TheWorld DOT com> 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On Monday 15 September 2003 06:07, Tim Prince wrote:
> On Sunday 14 September 2003 19:49, John D Rogers wrote:
> > Tim,
> >
> > Thanks for the information!  I hope ot put it to good use, especially the
> > part about copying the include directory to the location implied by
> > --prefix.
> >
My native builds and tests of the cygwin copy of gcc, obtained by setup, were 
OK, with the exception of java libraries, but including 
objc.  Test results, compared with results of past generic gcc-3.1.1 builds, 
and the test_installed results of the cygwin binary, were reasonably close.  

As Danny mentioned, one of the gcc testsuite cases reports failure, because 
-p is assumed to be synonymous with -pg.  However, all -pg tests will fail 
when mingw is installed, on account of linking with the wrong version of the 
library.  The work-around, if I may call it that, is to specify which library 
is to be used, in case someone wants to ask for the whole thing to be made a 
cygwin-specific selection in gcc testsuite.  The testsuite doesn't have any 
g77 -pg tests, so the lack of automation for that in cygwin doesn't show up.

2 of the gcc tests are failing, due to --enable-shared being turned on in the 
build.  I assume that the shared libraries are important enough to overlook 
those 2 failures.

So, to me, the main remaining mysteries are where to look for the 
cygwin-specific patches to be applied to generic gcc source, and how to make 
java build "out of the box."
-- 
Tim Prince

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