Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 8 Oct 2001 22:38:24 -0400 From: Christopher Faylor To: "'gcc-prs@gcc.gnu.org'" , "'cygwin@cygwin.com'" Subject: Re: c++/4479 can't build gcc-3.0.1 under cygwin Message-ID: <20011008223823.A22258@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'gcc-prs@gcc.gnu.org'" , "'cygwin@cygwin.com'" References: <8D00C32549556B4E977F81DBC24E985D40FFAC@crtsmail1.technol_exch.corp.riotinto.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8D00C32549556B4E977F81DBC24E985D40FFAC@crtsmail1.technol_exch.corp.riotinto.org> User-Agent: Mutt/1.3.21i I have no idea how stepping forward to a new version of the cygwin snapshot would solve this problem. *Possibly* this is alleviated by the recent auto-import changes to binutils, though. cgf On Tue, Oct 09, 2001 at 02:34:15AM -0000, Billinghurst, David (CRTS) wrote: >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)" >To: ; ; > >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/ -- cgf@cygnus.com Red Hat, Inc. http://sources.redhat.com/ http://www.redhat.com/ -- 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/