From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: limits.h bug in gcc
Date: Wed, 12 Sep 2001 13:33:00 -0000 [thread overview]
Message-ID: <200109122033.f8CKX9804687@constant.com> (raw)
> This is probably a stupid question, but is gcc 3.0.1 going to be
> fixed so it'll build as a cross compiler ? I'm trying to get it to
> build for arm-elf or sh-elf,
Rob, I strongly suggest trying to get powerpc-eabism working
first. For one thing, the ARM backend is not supported in gcc-3.0:
http://gcc.gnu.org/gcc-3.0/buildstat.html
You'll have better lucking picking backends that are represented on this list.
For another thing, the regression tester uses powerpc-eabism, so it
usually works. Look through this list and see when it's working:
http://gcc.gnu.org/ml/gcc-regression/2001-09/
best,
benjamin
next reply other threads:[~2001-09-12 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 13:33 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-12 8:53 [Bug-dejagnu] DejaGnu 1.4.1 fix Rob Savoye
2001-09-12 10:54 ` Gerald Pfeifer
2001-09-12 11:34 ` limits.h bug in gcc Rob Savoye
2001-09-13 4:57 ` Andrew Stubbs
2001-09-13 8:01 ` Rob Savoye
2001-09-13 8:49 ` Andrew Stubbs
2001-09-13 22:40 ` GNUTeam
2001-09-14 1:45 ` Andrew Stubbs
2001-09-14 3:42 ` GNUTeam
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=200109122033.f8CKX9804687@constant.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).