public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: alexs@redhat.com
Cc: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>,
	ecos-discuss@sourceware.cygnus.com, jens.ohlund@secrc.abb.se
Subject: Re: [ECOS] Problems making gcc
Date: Fri, 09 Jun 2000 07:37:00 -0000	[thread overview]
Message-ID: <39410124.AD145867@redhat.co.uk> (raw)
In-Reply-To: <NCBBKJPHEKGAJNNFGNBLEEBMFBAA.alexs@redhat.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
>   http://sourceware.cygnus.com/ml/cygwin-announce/2000/msg00023.html
> for details on the fixes and
>   http://sourceware.cygnus.com/cygwin/mirrors.html
> 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.

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

  reply	other threads:[~2000-06-09  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09  2:18 jens.ohlund
2000-06-09  4:15 ` Hugo 'NOx' Tyson
2000-06-09  4:26   ` Alex Schuilenburg
2000-06-09  7:37     ` Jonathan Larmour [this message]
2001-09-05  0:10   ` Hugo 'NOx' Tyson

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=39410124.AD145867@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=alexs@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=hmt@cygnus.co.ukx \
    --cc=jens.ohlund@secrc.abb.se \
    /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).