This is the mail archive of the
mailing list for the eCos project.
Re: Problems making gcc
- To: alexs at redhat dot com
- Subject: Re: [ECOS] Problems making gcc
- From: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Date: Fri, 09 Jun 2000 15:37:24 +0100
- CC: Hugo 'NOx' Tyson <hmt at cygnus dot co dot ukx>, ecos-discuss at sourceware dot cygnus dot com, jens dot ohlund at secrc dot abb dot se
- Organization: Red Hat UK Ltd.
- References: <NCBBKJPHEKGAJNNFGNBLEEBMFBAA.email@example.com>
Alex Schuilenburg wrote:
> > ISTR talking to our man Al, whom I have copied this msg, about a similar
> > thing yesterday. Al, can you shed any light on this?
> Yes. Switch to the latest cygwin1.dll (1.1.2) released on Wednesday. See
> for details on the fixes and
> on where to download.
Jens already said he was using 1.1.2, but read on.
> I managed to get around the problem initially by having the build directory
> mounted in text mode.
I'm somewhat sceptical that's the fix since the problem is on the drive
containing the sources, not the build tree.
No, my guess is that Jens installed the eCos patches to gcc 2.95.2 (which
include a patch to arm.h) when using cygwin 1.1.1, and then found this
problem and *then* updated to cygwin 1.1.2. By that point it was too late -
arm.h already had got CRs put in it.
So instead, now that Jens is using 1.1.2, he should unpack the original
tarball again and reapply the patches. All should then be happy.
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault