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@sources.redhat.com
Subject: Re: [ECOS] Problem building latest gcc
Date: Tue, 06 Feb 2001 05:21:00 -0000	[thread overview]
Message-ID: <3A7FFA4F.47B78F97@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010205192508.00a96c10@larwe.com>

"Lewin A.R.W. Edwards" wrote:
> 
> I _REALLY_ want to try to get ARM Thumb support working, so I downloaded
> the latest gcc snapshot, configured it as per
> sources.redhat.com/ecos/tools/win-thumb-elf.html, and then tried to make
> it. Unfortunately it died a short way into the make process, with the
> following [abbreviated!] make.out. I killed it when it had created about
> 260K of the following garbage. Any ideas on this? :(
> 
> make[1]: Entering directory `/tmp/build/gcc/gcc'
> Expect 33 shift/reduce conflicts and 58 reduce/reduce conflicts.
> cd /src/gcc/gcc-20010205/gcc/cp; bison  -d -o p$$.c parse.y ; \
> grep '^#define[         ]*YYEMPTY' p$$.c >> p$$.h ; \
> mv -f p$$.c parse.c ; mv -f p$$.h parse.h
> parse.y:21: unknown character: \15
> parse.y:21:    Skipping to next %
> parse.y:220: unknown character: \15
> parse.y:220:    Skipping to next %
> parse.y:222: unknown character: \15
> parse.y:222:    Skipping to next %
> parse.y:231: unknown character: \15

Perhaps the version of bison you are using does not correspond to what GCC
developers expect? Otherwise follow up on gcc@gcc.gnu.org methinks.

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-02-06  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 16:31 Lewin A.R.W. Edwards
2001-02-06  5:21 ` Jonathan Larmour [this message]
2001-02-06  6:13   ` Lewin A.R.W. Edwards
2001-02-06  6:50     ` Jonathan Larmour
2001-02-06  7:12       ` Lewin A.R.W. Edwards

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=3A7FFA4F.47B78F97@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.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).