public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "D. A. M. Revok" <marvin@synapse.net>
Cc: 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 10:26:06 +0100	[thread overview]
Message-ID: <20020724102606.B25115@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E17XIMe-0001kA-00@caramon.arm.linux.org.uk>; from marvin@synapse.net on Wed, Jul 24, 2002 at 05:23:12AM -0400

On Wed, Jul 24, 2002 at 05:23:12AM -0400, D. A. M. Revok wrote:
> 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.

When building a kernel, paths specified with the gcc -I flag are searched
first, then the default include directory paths.

In later kernels, gcc is told not to use the default include directory
paths to stop it looking there and picking up an old header file.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2002-07-24  9:22 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
     [not found]       ` <E17XIMe-0001kA-00@caramon.arm.linux.org.uk>
2002-07-24  9:26         ` Russell King [this message]
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=20020724102606.B25115@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marvin@synapse.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