From: Nix <nix@esperi.org.uk>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem compiling 2.6.12
Date: Thu, 23 Jun 2005 12:08:13 +0100 [thread overview]
Message-ID: <87r7et2uw2.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200506222253.47777.nick@linicks.net> (Nick Warne's message of "22 Jun 2005 23:13:10 +0100")
On 22 Jun 2005, Nick Warne stipulated:
> Is it? I thought kernel didn't care what Glibc or what kernel headers you had
> (that is system requirement) - it is automous. Isn't HOSTCC explicitly just
> what compiler you have?
HOSTCC is a non-cross-compiler, i.e. for building userspace stuff to run
on the build machine. There are a number of such things built during a
normal kernel build (code generators, the config system, et al) and they
use the C library just like any userspace app does.
--
`It's as bizarre an intrusion as, I don't know, the hobbits coming home
to find that the Shire has been taken over by gangsta rappers.'
next prev parent reply other threads:[~2005-06-23 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 19:37 Problem compiling 2.6.12 Nick Warne
2005-06-22 21:30 ` Adrian Bunk
2005-06-22 21:53 ` Nick Warne
2005-06-23 9:53 ` Adrian Bunk
2005-06-23 11:08 ` Nix [this message]
[not found] <Pine.LNX.4.62.0506240856460.10920@eagle.netwrx1.com>
[not found] ` <42BC1C43.3040505@blueyonder.co.uk>
[not found] ` <Pine.LNX.4.62.0506241258500.20958@eagle.netwrx1.com>
[not found] ` <42BC9FF1.1010400@blueyonder.co.uk>
[not found] ` <5nerb117olj7kahv0k8b1vss382ini6bfr@4ax.com>
2005-06-26 0:39 ` Sid Boyce
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 21:26 Sid Boyce
2005-06-22 15:28 George Kasica
2005-06-22 15:59 ` Jesper Juhl
2005-06-22 16:44 ` Adrian Bunk
2005-06-22 19:15 ` George Kasica
2005-06-22 19:26 ` Jesper Juhl
2005-06-22 19:14 ` George Kasica
2005-06-22 19:45 ` Richard B. Johnson
2005-06-22 16:42 ` Adrian Bunk
2005-06-22 19:22 ` George Kasica
2005-06-22 21:33 ` Adrian Bunk
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=87r7et2uw2.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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