mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Tibor Kendl <kendl@flexys.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Set gcc to kernel header path
Date: Fri, 27 Feb 2004 08:33:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0402270823500.6853@chaos> (raw)
In-Reply-To: <403F4B58.1010901@flexys.hu>

On Fri, 27 Feb 2004, Tibor Kendl wrote:

> Dear mailing list members!
>
> I'd like to know, how do you solve this problem on your own systems.
> I've installed a linux distribution with a 2.2.18 kernel, than i've
> downloaded, compiled and installed a 2.6.2 kernel. How can i make, if i
> want to compile any application ( like Samba, Apache, KDE, etc...), the
> gcc compiler use the '/usr/src/linux-2.6.2/include' header path instaead
> of the '/usr/include' for such include directories like 'linux', 'asm',
> 'asm-generic', etc...?
>
> Yours
> Tibor Kendl
>


	gcc -I/usr/src/linux-2.6.2/include

... if you are sure that's what you want. Normally, you use the
headers that your 'C' runtime library was compiled with, i.e.,
what's in /usr/include.

gcc will search the -I/path first, then do the other ones unless
you use  -nostdinc on the command-line as well. If you use
-nostdinc, you need to also put -I`gcc -print-file-name=include` on
the command line, also or else gcc won't find stddef.h, etc., which
are not in one of the "standard places".


Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



      reply	other threads:[~2004-02-27 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 13:51 Tibor Kendl
2004-02-27 13:33 ` Richard B. Johnson [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=Pine.LNX.4.53.0402270823500.6853@chaos \
    --to=root@chaos.analogic.com \
    --cc=kendl@flexys.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®