public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Problem downloading eCos
Date: Wed, 21 Mar 2001 10:09:00 -0000	[thread overview]
Message-ID: <3AB8EE4F.A6B85788@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010321124145.00b5ee28@mail.larwe.com>

"Lewin A.R.W. Edwards" wrote:
> 
> Hi Jonathan,
> 
> > > I'm just updating my gcc sources to the latest right now, then I will
> >
> >arm-elf is certainly what I used, and I invoked arm-elf-gcc with -mthumb. I
> 
> Silly, silly, silly, stupid, forgetful me. I forgot that current versions
> of gcc are broken in cygwin. 2.95.2 is the last version that seems to build
> properly. Here's the output from the current sources.
[snip]
> ./gencodes.exe /src/gcc/gcc/config/arm/arm.md > tmp-codes.h
> 'src/gcc/gcc/config/arm/arm.md:36: unknown rtx code `define_constants
> /src/gcc/gcc/config/arm/arm.md:36: following context is
> `  [(IP_REGNUM      12);
>   Scratch register'
> make[1]: *** [s-codes] Error 1
> make[1]: Leaving directory `/tmp/build/gcc/gcc'
> make: *** [all-gcc] Error 2
> make: Leaving directory `/tmp/build/gcc'

Looks suspiciously like our old friend the CRLF problem. It's barfed on the
very first non-comment line.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-03-21 10:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21  6:04 Daniel.Andersson
2001-03-21  6:13 ` Lewin A.R.W. Edwards
2001-03-21  8:14   ` Jonathan Larmour
2001-03-21  8:21     ` Lewin A.R.W. Edwards
2001-03-21  8:25       ` Jonathan Larmour
2001-03-21  8:36         ` Lewin A.R.W. Edwards
     [not found]           ` <3AB8D972.43A4B1B1@redhat.com>
2001-03-21  9:44             ` Lewin A.R.W. Edwards
2001-03-21 10:09               ` Jonathan Larmour [this message]
2001-03-21 10:15                 ` Lewin A.R.W. Edwards
2001-03-21 11:45                 ` Lewin A.R.W. Edwards
2001-03-21 12:42                   ` Jonathan Larmour
2001-03-21 13:13                     ` Lewin A.R.W. Edwards
2001-03-21 11:49                 ` Lewin A.R.W. Edwards
2001-03-21 13:29                   ` Jonathan Larmour
2001-03-21 13:48                     ` Lewin A.R.W. Edwards
2001-03-22  8:27                     ` Lewin A.R.W. Edwards
2001-03-22 11:37                       ` Jonathan Larmour
2001-03-22 11:39                         ` Lewin A.R.W. Edwards
  -- strict thread matches above, loose matches on Subject: below --
2001-03-20 23:45 Daniel.Andersson
2001-03-20 23:52 ` Jonathan Larmour
2001-03-21  0:47   ` massey steven
2001-03-21  5:54 ` Lewin A.R.W. Edwards
2001-03-20  8:07 Daniel.Andersson
2001-03-20  8:12 ` Jonathan Larmour
2001-03-20  8:18   ` Lewin A.R.W. Edwards
2001-03-20  9:41     ` Jonathan Larmour
2001-03-20  8:17 ` Lewin A.R.W. Edwards
2001-03-20  7:43 Daniel.Andersson
2001-03-20  7:53 ` Jonathan Larmour
2001-03-20  8:15 ` Jesper Skov

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=3AB8EE4F.A6B85788@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=larwe@larwe.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).