Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3A0B7DD7.B295D300@ece.gatech.edu>
Date: Thu, 09 Nov 2000 23:47:19 -0500
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: cygwin@sources.redhat.com
Subject: Re: Can not found crt1.o when using -mno-cygwin option
References: <002101c04a1d$60ae0c20$de90718c@cm.nctu.edu.tw> <3A0AE178.7FF31F35@ece.gatech.edu> <20001109232939.A6759@redhat.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Christopher Faylor wrote:
> 
> On Thu, Nov 09, 2000 at 12:40:08PM -0500, Charles S. Wilson wrote:
> >There seem to be a few mistakes in the specs file; the following seems
> >to work (however, the "right" fix is somewhere in the bowels of the gcc
> >source code, so that the specs file is *generated* to look like this).
> >
> >#1) The specs file is using the wrong version number
> 
> I don't know how this matters.  This version isn't reported by gcc and
> it obviously isn't used for getting the specs file.  I have, however,
> updated my script to deal with this.  The problem is that the specs file
> is generated by the compiler building gcc rather than gcc itself when
> building gcc as a cross-compile.  That's what I do.

It probably doesn't matter.  I just noticed it because "gcc -v" showed
"version 2.95.2-3" and I knew that was wrong.  Then, I saw it in the
spec file while tracking down the libmingw thing.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com