From: Adrian Bunk <bunk@stusta.de>
To: George Kasica <georgek@netwrx1.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem compiling 2.6.12
Date: Wed, 22 Jun 2005 23:33:52 +0200 [thread overview]
Message-ID: <20050622213352.GB3749@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0506221415460.25918@eagle.netwrx1.com>
On Wed, Jun 22, 2005 at 02:22:10PM -0500, George Kasica wrote:
> I have no idea what you are referring to there. If you can give me details
> on what information you need or what you need me to do here I'll try to
> provide it. I'm unfortunately not a kernel hacker or programmer here.
Where does /usr/local/include/ come from, what is it linked to,... ???
/usr/include contains a copy of kernel headers shipped by your glibc.
/path/to/your/kernel/sources/include contains a copy of kernel headers
shipped with the kernel you are trying to compile.
But where do these kernel headers under /usr/local/include/ come from?
> George
>
> >On Wed, Jun 22, 2005 at 10:28:25AM -0500, George Kasica wrote:
> >>Hello:
> >>
> >>Trying to compile 2.6.12 here and am getting the following error. I am
> >>currently running 2.4.31 and have upgraded the needed bits per the Change
> >>document before trying the build:
> >>
> >>[root@eagle src]# cd linux
> >>[root@eagle linux]# make mrproper
> >> CLEAN .config
> >>[root@eagle linux]# cp ../config-2.4.31 .config
> >>[root@eagle linux]# make oldconfig
> >> HOSTCC scripts/basic/fixdep
> >>In file included from /usr/local/include/netinet/in.h:212,
> >>...
> >
> >What are these kernel headers under /usr/local ?
> >I don't see any reason why they should be there.
> >
> >>George
> >
> >cu
> >Adrian
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-06-22 21:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 15:28 Problem compiling 2.6.12 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-22 19:37 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
2005-06-23 21:26 Sid Boyce
[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
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=20050622213352.GB3749@stusta.de \
--to=bunk@stusta.de \
--cc=georgek@netwrx1.com \
--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.