From: Jeffrey A Law <law@cygnus.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Cross compilation vs. libiberty
Date: Thu, 03 Aug 2000 00:38:00 -0000 [thread overview]
Message-ID: <29862.965288349@upchuck> (raw)
In-Reply-To: <20000802182521R.mitchell@codesourcery.com>
In message < 20000802182521R.mitchell@codesourcery.com >you write:
>
> Folks --
>
> I have run into the problem where libiberty, only configured once,
> does not build for the target since the target configuration does not
> match the host. In particular, I have stdlib.h on the host, but not
> on the target, but files in libiberty want to include stdlib.h because
> the host configury indicates that is the right thing to do.
Sounds like a configury problem of some kind.
> Jeff, I remember you were against rerunning configure. Please
> remind me why, or point me at a concise email summarizing your
> thinking, if it's available.
I was against rerunning it for the different stages of building gcc itself
because, in theory, there shouldn't be any differences between the
result between stages.
jeff
prev parent reply other threads:[~2000-08-03 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 18:25 Mark Mitchell
2000-08-02 18:36 ` Geoff Keating
2000-08-02 18:42 ` Mark Mitchell
2000-08-02 18:39 ` Alexandre Oliva
2000-08-03 0:38 ` Jeffrey A Law [this message]
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=29862.965288349@upchuck \
--to=law@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).