From: Alexandre Oliva <aoliva@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Cross compilation vs. libiberty
Date: Wed, 02 Aug 2000 18:39:00 -0000 [thread overview]
Message-ID: <or1z07t96n.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20000802182521R.mitchell@codesourcery.com>
On Aug 2, 2000, Mark Mitchell <mark@codesourcery.com> wrote:
> 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.
libiberty is configured and built for the target with CC_FOR_TARGET,
after GCC is built. Isn't a libiberty directory created within the
target sub-directory of the build tree?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-08-02 18:39 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 [this message]
2000-08-03 0:38 ` Jeffrey A Law
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=or1z07t96n.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.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).