From: Rupert Wood <rup@kanat.pair.com>
To: David Meggy <dmeggy@techsol.ca>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: gcc 3.2 limits.h from crtstuff.c
Date: Tue, 03 Sep 2002 01:43:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.30.0209030442290.1320-100000@kanat.pair.com> (raw)
In-Reply-To: <1031004187.410.21.camel@DavidAsus>
Dave Meggy wrote:
> I think there is something wrong with the way it finds includes.
I'm not on my usual system so I can't verify this, but from memory:
> According to my inserted #warnings ${my cross env}/include/limits.h
> is never called.
I've had disagreements in the past about where things should live, but I
think the headers should be in
$(my cross env)/arm-linux/sys-include
and libraries
$(my cross env)/arm-linux/lib
These are the paths used by GCC's configure's --with-headers and
--with-libs. Kai on the crossgcc list will tell you that the headers
should actually go in
$(my cross env)/arm-linux/include
but I think he's wrong :-)
> and the compiler I'm trying to build was configured like this
> {gcc_source_path}/configure --target=arm-linux --host=arm-linux \
> --build=i386-pc-linux-gnu --prefix=${my cross runtime env} \
> --enable-languages=c --disable-multilib \
> --disable-threads --disable-shared
Since you're neither specifying --with-headers or --with-libs (which is
fine if they're already in place) you need to specify --without-newlib.
Hope that helps,
Rup.
next prev parent reply other threads:[~2002-09-03 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 15:11 David Meggy
2002-09-03 1:43 ` Rupert Wood [this message]
2002-09-03 8:07 ` David Meggy
2002-09-03 8:53 ` David Meggy
2002-09-03 9:17 ` David Meggy
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.BSF.4.30.0209030442290.1320-100000@kanat.pair.com \
--to=rup@kanat.pair.com \
--cc=dmeggy@techsol.ca \
--cc=gcc-help@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).