Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com X-Authentication-Warning: atacama.four-d.de: mail set sender to using -f Date: Tue, 17 Dec 2002 10:12:47 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) From: Thomas Pfaff To: cygwin-developers AT cygwin DOT com Subject: Re: building the gcc-3.2-3 bootstrap fails on libstdc++-v3 In-Reply-To: Message-ID: X-X-Sender: pfaff AT antarctica DOT intern DOT net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 16 Dec 2002, Christopher Faylor wrote: > On Mon, Dec 16, 2002 at 03:26:27AM -0800, James Michael DuPont wrote: > >As promised, I have started to check the releases > >of cygwin by bootstrapping them. > >This one got pretty far, all the way to libstdc++-v3. > > > >The error is : > >../../../../include/getopt.h:115: declaration of C function `int > >getopt()' > > conflicts with > >/usr/include/sys/unistd.h:125: previous declaration `int getopt(int, > >char* const*, const char*)' here > > In case it isn't clear, I *do not care* about this problem. I am able to > build gcc myself with no problem. I *don't care* if it doesn't work for > you since the fix is so completely trivial. > > If you want to suggest a fix that goes beyond making the obvious change > to ../include/getopt.h, then send it to the gcc mailing list. > Otherwise, these reports are just noise here. > > You've got a functional gcc compiler use it. If you want to build it yourself, > then fix the source and move on. > > How many times do I have to say this??? Chris, IMHO the easiest way to fix this is to remove the getopt prototype from unistd.h and include getopt.h instead. This will define HAVE_DECL_GETOPT and the build will not fail. I might create a patch if you agree. Otherwise you have to say this again and again i suppose. Thomas