Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <8D00C32549556B4E977F81DBC24E985D40FFAC@crtsmail1.technol_exch.corp.riotinto.org>
From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "'David Abrahams'" <david.abrahams@rcn.com>
Cc: "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>,
   "'cygwin@cygwin.com'"
	 <cygwin@cygwin.com>
Subject: RE: c++/4479  can't build gcc-3.0.1 under cygwin 
Date: Tue, 9 Oct 2001 02:34:15 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"

I suspect we are all right :->

I have just built gcc-3.0.1 (release) using snapshot cygwin1.dll and headers
on win2k.  I know it works with previous cygwin releases (but I forget which
ones).

Your build (and others) with current cygwin release fails, and trying
snapshot cygwin1.dll only failed.  Points to a recently introduced header
problem, as you indicate.

I haven't reproduced your problem today (although I saw it on another PC of
mine), but it has been solved by:
 * stepping back to a previous cygwin release (forget which),
 * stepping forward to snapshot cygwin1.dll + headers
 * patching libiberty so that gcc-3.0.2 will work (done by cgf)
 * your work around below

If you are happy I will close the PR.

-----Original Message-----
From: David Abrahams [mailto:david.abrahams@rcn.com]
Sent: Tuesday, 9 October 2001 1:20 
To: Billinghurst, David (CRTS); billingd@gcc.gnu.org;
gcc-gnats@gcc.gnu.org
Subject: Re: c++/4479


#defining HAVE_SYS_ERRLIST and HAVE_SYS_NERR in both libiberty/config.h and,
for bootstrapping, in i686-pc-cygwin/libiberty/config.h allows the build and
install process to complete successfully. I think this evidence clearly
shows that the problem does not lie with the cygwin DLL.

HTH,
Dave

===================================================
  David Abrahams, C++ library designer for hire
 resume: http://users.rcn.com/abrahams/resume.html

        C++ Booster (http://www.boost.org)
          email: david.abrahams@rcn.com
===================================================

----- Original Message -----
From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: <billingd@gcc.gnu.org>; <gcc-gnats@gcc.gnu.org>;
<david.abrahams@rcn.com>
Sent: Monday, October 08, 2001 1:01 AM
Subject: Re: c++/4479


> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4479&database=gcc
>
> This is a problem with the current cygwin1.dll.  It has been discussed on
> the cygwin mailing list and has been fixed in cvs and recent cygwin
> snapshots.  Suggest you download a cygwin snapshot, or wait till the next
> cygwin release.
>

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

