All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Josh Huber <huber@mclx.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: problems about __cli()
Date: Thu, 20 Jul 2000 14:45:56 +0100	[thread overview]
Message-ID: <200007201345.OAA29151@hyperion.valhalla.net> (raw)


Thu, Jul 20, 2000,  Josh Huber wrote:
> On Thu, Jul 20, 2000 at 10:19:54AM +0100, Iain Sandoe wrote:
>>
> [snip]
>>
>> It is *vital* to make sure that there is a symlink named 'linux' in /usr/src
>> that points to your /usr/src/your-kernel-foo-bar/ because there are symlinks
>> in /usr/include that expect to use this to find the build-specific headers.
>
> A couple notes:
>
> You don't have to put your kernel in /usr/src, and you DON'T have to
> symlink /usr/src/linux to it before you build.  The symlinks (on
> broken RedHat derivatives) in /usr/include should point to the kernel
> headers that your libc was built againt, otherwise you risk breaking
> binary compatibility.

I guess I *must* have one of those broken derivatives... and it doesn't work
for me without that step...  Admittedly, this is mostly an issue between
2.2.xx and 2.4.0 - but I do have to remember to change it back between
whiles... a better way would be ?

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-20 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-20 13:45 Iain Sandoe [this message]
2000-07-20 15:44 ` problems about __cli() Josh Huber
2000-07-22 14:10   ` Geert Uytterhoeven
2000-07-22 18:11     ` Martin Costabel
2000-07-24 12:19       ` Josh Huber
2000-07-24 15:01         ` Jeff Garzik
2000-07-21 14:15 ` Michel Dänzer
  -- strict thread matches above, loose matches on Subject: below --
2000-07-21 14:37 Iain Sandoe
2000-07-20  9:19 Iain Sandoe
2000-07-20 12:55 ` Josh Huber
2000-07-20 13:36 ` Michael Schmitz
2000-07-20  7:29 Rolf Liu

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=200007201345.OAA29151@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=huber@mclx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.