public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "David T. Schneider" <dschneider@socsolutions.com>
To: <cygwin@cygwin.com>
Subject: RE: Binutils and GCC
Date: Tue, 18 Sep 2001 13:50:00 -0000	[thread overview]
Message-ID: <4935FB7B7B5AD4118D8B0090276ADB8F053FBA@pdc01.SoCSolutions.com> (raw)

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@acm.org ] 
Sent:	Tuesday, September 18, 2001 2:47 AM
To:	cygwin@cygwin.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/



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

             reply	other threads:[~2001-09-18 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18 13:50 David T. Schneider [this message]
2001-09-18 14:22 ` Larry Hall (RFK Partners, Inc)
2001-09-18 15:43   ` Christopher Faylor
2001-09-18 15:57     ` Larry Hall (RFK Partners, Inc)
2001-09-18 16:36       ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2001-09-20  8:24 Binutils and GCC [LONG and mildly OT] Christopher Faylor
2001-09-20 12:30 ` Binutils and GCC Christopher Currie
2001-09-18  0:05 Doug Johnson
2001-09-18  8:46 ` Christopher Faylor
2001-09-17 17:24 Jason.Kajita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4935FB7B7B5AD4118D8B0090276ADB8F053FBA@pdc01.SoCSolutions.com \
    --to=dschneider@socsolutions.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).