From: Andrew Stubbs <Andrew.Stubbs@st.com>
To: rob@welcomehome.org
Cc: pfeifer@dbai.tuwien.ac.at, gcc@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: limits.h bug in gcc
Date: Thu, 13 Sep 2001 04:57:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10109131242560.5441-100000@absolut> (raw)
In-Reply-To: <20010912123230.J224@welcomehome.org>
On Wed, 12 Sep 2001 rob@welcomehome.org wrote:
> On Wed, Sep 12, 2001 at 07:54:45PM +0200, Gerald Pfeifer wrote:
>
> > That would be great, thanks! (Would you mind sending the announcement
> > also to gcc@gcc.gnu.org in this case?)
>
> 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, so I can test the cross testing support in DejaGnu. I saw the same
> bug in GCC 3.0, where the script that generates the limits.h file was hardcoded
> to only work on a native system.
>
> I guess I'll drop back to gcc 2.95.3 to build a cross complier, but I was
> hoping 3.0.1 would have this fixed. Gcc 3.0.1 also doesn't build natively with
> --enable-threads either...
>
> from ../../../../gcc-3.0.1/gcc/libgcc2.c:1166:
> /home/rob/projects/gnu/obj/redhat/arm-elf/gcc/include/limits.h:125:75: limits.h: No such file or directory
> make[2]: *** [libgcc/./_fixunsdfsi.o] Error 1
>
> - rob -
I have absolutly no trouble building and using an sh-elf cross compiler
under cygwin, solaris and linux using newlib. I have successfully built
both 3.0 and 3.0.1. As far as I am concerned the target can be added to
the list on the web site.
On the other hand I did have a lot of trouble getting dejagnu working - I
have managed to get it cobbled together after a lot of grief so that it
works. Best of luck fixing it!
------------------------------------------------------------------------
| Andrew Stubbs, | E-mail: Andrew.Stubbs@st.com |
| STMicroelectronics Ltd., | or stubbsa@bristol.st.com |
| 1000 Aztec West, | |
| Almondsbury, | Tel: +44 (0)1454 462325 |
| Bristol, BS32 4SQ, U.K. | Fax: +44 (0)1454 617910 |
------------------------------------------------------------------------
next prev parent reply other threads:[~2001-09-13 4:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 7:38 DejaGnu 1.4.1 fix Gerald Pfeifer
2001-09-12 7:43 ` Joseph S. Myers
2001-09-12 8:53 ` [Bug-dejagnu] " Rob Savoye
2001-09-12 9:15 ` Alex Buell
2001-09-12 9:26 ` Rob Savoye
2001-09-12 10:54 ` Gerald Pfeifer
2001-09-12 10:59 ` Jakub Jelinek
2001-09-12 11:10 ` Rob Savoye
2001-09-12 11:34 ` limits.h bug in gcc Rob Savoye
2001-09-13 4:57 ` Andrew Stubbs [this message]
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
2001-09-12 13:33 Benjamin Kosnik
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=Pine.GSO.4.10.10109131242560.5441-100000@absolut \
--to=andrew.stubbs@st.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=rob@welcomehome.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).