From: Eric Noack <eric.noack@gmx.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo kernel setup question
Date: Tue, 17 Sep 2002 09:44:50 +0200 [thread overview]
Message-ID: <20020917094450.35656036.eric.noack@gmx.de> (raw)
In-Reply-To: <20020917091727.1eb93581.bain@reaper.org>
Am Tue, 17 Sep 2002 09:17:27 +0200
schrieb Henti Smith <bain@reaper.org>:
> Hi there :)
>
> Just a quick question regarding the include files for linux kernel on gentoo.
>
> I see as with most distro's there is a header and source install (emerge)
> so when I update to the latest source ... does this update the headers as well ?
>
> I'm asking this as I saw that /usr/include/linux and /usr/include/asm is actual directories.
> I usually soft link /usr/include/linux to /usr/src/linux/include/linux and /usr/include/asm to /usr/src/linux/include/asm-i386
> and since /usr/src/linux is linked to current kernel .. I always have my running kernel headers for everything else ?
>
> Is this a bad way of doing things ...
>
> comments ?
>
It actually is a bad way of doing things,
the headers in /usr/include should always keep the same you did compile the important librarys like glibc to.
if you replace this headers and there actually is a change in them you have to re-compile everything that uses that part,
which would be glibc, Xlibs, ..., ...
so its just usual to keep the header version there u used to compile glibc.
Corvus V Corax
> Henti Smith
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
next prev parent reply other threads:[~2002-09-17 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 7:17 [gentoo-dev] Gentoo kernel setup question Henti Smith
2002-09-17 7:44 ` Eric Noack [this message]
2002-09-17 7:51 ` Henti Smith
2002-09-18 3:54 ` [gentoo-dev] " Paul
2002-09-17 8:46 ` [gentoo-dev] " Wilbert Berendsen
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=20020917094450.35656036.eric.noack@gmx.de \
--to=eric.noack@gmx.de \
--cc=gentoo-dev@gentoo.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