From: Kevin Buettner <kev@primenet.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] problem building gnu tool
Date: Fri, 19 May 2000 19:16:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205102@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205100@msgid-missing>
On May 19, 3:07pm, Russell Mok wrote:
> I download the source on a redhat 5.2 machine and try to build a cross
> compiler for ia64. The build fails because unistd.h and other system
> headers are missing. I tried to make configure to think I don't have
> any system headers using --with-headers=empty-dir and
> --without-headers but neither worked.
Why don't you just extract the header files from the glibc and kernel
RPMS? Actually, to be useful, you'll need the libraries too. But
those are also available in the RPM. (When you install these RPMS,
you'll want to use the --root option to cause the RPM to be installed
at a different location than normal. You might also need the
--ignorearch option.)
Kevin
--
Kevin Buettner
kev@primenet.com, kevinb@redhat.com
prev parent reply other threads:[~2000-05-19 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 19:07 [Linux-ia64] problem building gnu tool Russell Mok
2000-05-19 19:13 ` Jim Wilson
2000-05-19 19:16 ` Kevin Buettner [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=marc-linux-ia64-105590678205102@msgid-missing \
--to=kev@primenet.com \
--cc=linux-ia64@vger.kernel.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