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
Date: Tue, 18 Sep 2001 18:44:11 -0400
From: Christopher Faylor <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Binutils and GCC
Message-ID: <20010918184411.C8571@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4935FB7B7B5AD4118D8B0090276ADB8F053FBA AT pdc01 DOT SoCSolutions. <4 DOT 3 DOT 1 DOT 2 DOT 20010918171957 DOT 030f8ed8 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.1.2.20010918171957.030f8ed8@pop.ma.ultranet.com>
User-Agent: Mutt/1.3.21i

On Tue, Sep 18, 2001 at 05:23:21PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>The best suggestion I can offer is the obvious, but I'll state it in case
>it hasn't occurred to someone who would like to help resolve it.  Debugging
>the Cygwin DLL is probably the most informative approach to isolating the 
>problem.

Actually, there is no Cygwin DLL debugging involved.

Unless I am missing something, this is a compile time error in
libiberty.  The fix should be extremely obvious.  Since the people
building the tools are all apparently C programmers I am not sure why no
one has proposed a fix yet.

Actually, I've already suggested one solution which seems to have been
ignored.

Instead, people seem to be adopting the typical Microsoft user way of
thinking: "Hmm.  1.3.3 not work.  Me downgrade to 1.3.2...  Now let me
reboot many times...  It work! Problem am solved!"

It is inconceivable (even for this mailing list) that we keep discussing
this and none of the affected parties have bothered to look at what's
failing.  People have apparently been stalled for days because of a
simple C compilation error!  Wow.

cgf

>At 04:49 PM 9/18/2001, David T. Schneider wrote:
>>I have managed to revert to cygwin 1.3.2 and now both the ARM cross
>>builds and the native builds are running.  As far as I can determine,
>>the cygwin package is the only thing different between the two
>>environments.  Are there any suggestions on how to isolate the cause of
>>the failures?
>>
>>David T. Schneider
>>Chief Technical Officer
>>SoC Solutions, L.L.C.
>>
>>  -----Original Message-----
>>From:   Doug Johnson [mailto:finson AT acm DOT org] 
>>Sent:   Tuesday, September 18, 2001 2:47 AM
>>To:     cygwin AT cygwin DOT com
>>Subject:        RE: Binutils and GCC 
>>
>>I am having a similar experience.  I built a cross compiling gcc for 
>>W98->MIPS last week using 1.3.2.  Today I rebuilt my system from bare
>>metal 
>>to run W2K.  Everything else is fine, but I cannot compile binutils
>>using 
>>1.3.3.  I get the same error that David is getting.
>>
>>I have tried to revert to 1.3.2, but that doesn't work because for some 
>>reason setup now believes that the cygwin package should be 
>>cygwin-1.3.2-1.tar.bz2 (rather than cygwin-1.3.2-1.tar.gz, which is what
>>I 
>>have from my previous install).
>>
>>So I'm kind of toast for the moment.  Any guidance would be helpful.
>>
>>Thanks.
>>
>>Doug Johnson
>>
>>Jason Kajita  wrote:
>>
>> >David T. Schneider" <dschneider at socsolutions dot com> wrote:
>> >... When I try to build the tools to compile ARM code on CygWin
>> >following the direction supplied for building ecos I get:
>> >/usr/src/binutils-2.10.1/libiberty/strerror.c:461: conflicting types
>>for
>> >`sys_errlist'
>> >/usr/include/sys/errno.h:23: previous declaration of `sys_errlist'
>> >when the make reaches /usr/src/binutils-2.10.1/libiberty/strerror.c
>> >
>> >I've also tried performing a native build for gcc-2.95.3 and gcc-3.0.1
>> >and get the same error.  ...
>> >
>> >=======================================================================
>>=
>>>Further information on the issue:
>>>I have believe that this problem may be related to the 1.3.3
>>>cygwin1.dll release.  When I revert back to 1.3.2-1, I do not get the
>>>error.

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