From: David Edelsohn <dje@watson.ibm.com>
To: Elizabeth Clarke <eclarke@aminocom.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc-2.1.2 cross-compile problem
Date: Wed, 26 Apr 2000 12:58:39 -0400 [thread overview]
Message-ID: <200004261658.MAA22540@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Elizabeth Clarke <eclarke@aminocom.com> of "Wed, 26 Apr 2000 14:37:25 -0000." <3906FF25.4E9E6AEA@aminocom.com>
The cross-tools want to have the target system header files
available in a directory called "sys-include" underneath the target
triplet in the installation directory. The target triplet directory wants
to look like /usr on the real system and the gcc-fixed header files will
go into the regular "include" directory.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-26 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-20 16:43 glibc-2.1.2 cross-compile problem Elizabeth Clarke
2000-04-26 0:24 ` Graham Stoney
2000-04-26 14:37 ` Elizabeth Clarke
2000-04-26 16:58 ` David Edelsohn [this message]
2000-04-26 19:01 ` Matt Porter
2000-04-27 14:22 ` Elizabeth Clarke
2000-04-28 0:42 ` Graham Stoney
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=200004261658.MAA22540@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=eclarke@aminocom.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).