All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D.A.M. Revok" <marvin@synapse.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2
Date: Wed, 24 Jul 2002 05:23:12 -0400	[thread overview]
Message-ID: <20020724092002Z315468-685+17104@vger.kernel.org> (raw)
In-Reply-To: <20020724101620.A25115@flint.arm.linux.org.uk>

Oh, I didn't know that. . .
  How's it supposed to know which version to include if there are 2 versions. 
. . hmmm . . . probably by specifying somesort of include-path that puts 'em 
in order-of-preference, then.

Thanks for setting me straight: stress is a bad caffeine-substitute, eh?
( actually, caffeine is an effective stress-substitute, methinks )

On Wed  24 July, 2002 05:16, you wrote:
> On Wed, Jul 24, 2002 at 05:03:52AM -0400, D. A. M. Revok wrote:
> > Oh, fucking great, /usr/include/asm /isn't/ a symlink to
> > /usr/src/linux/include/asm, it's its own directory.
>
> That's 100% correct.  /usr/include/asm and /usr/include/linux are supposed
> to be the kernel headers glibc was compiled with, not the kernel headers
> for the kernel you're trying to build.

  reply	other threads:[~2002-07-24  9:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  8:29 Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2 D.A.M. Revok
     [not found] ` <20020724084749.GC15043@dreams.soze.net>
2002-07-24  9:03   ` D.A.M. Revok
2002-07-24  9:16     ` Russell King
2002-07-24  9:23       ` D.A.M. Revok [this message]
     [not found]       ` <E17XIMe-0001kA-00@caramon.arm.linux.org.uk>
2002-07-24  9:26         ` Russell King
2002-07-25  4:32       ` Brad Hards
2002-07-25  7:57         ` Russell King
2002-07-25  8:23           ` kernel ABI [was something about Compile Bogons...] Brad Hards
2002-07-24  9:31 ` Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2 Alex Riesen

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=20020724092002Z315468-685+17104@vger.kernel.org \
    --to=marvin@synapse.net \
    --cc=linux-kernel@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 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.