Now I have emerged kernel-headers-2.4.21. Indeed /usr/include/linux was downgraded from 2.6.1 to 2.4.21, also portage officially did not downgrade anything. This was a quite overwrite...

In the end I see two interesting messages:

* Kernel headers are usually only used when recompiling glibc, as such, following the installation
* of newer headers, it is advised that you re-merge glibc as follows:
* emerge glibc
* Failure to do so will cause glibc to not make use of newer features present in the updated kernel
* headers.


Is this really serious? My glibc was compiled with linux-2.4.20-gentoo-r9 headers (I suppose, as that was my installation kernel).

And:

* Regenerating GNU info directory index...
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info.gz'
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info-1.gz'
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info-2.gz'
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info.gz'
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info-1.gz'
install-info: warning: no info dir entry in `/usr/share/info/g-wrap.info-2.gz'
* Processed 1046 info files; 6 errors.


What those mean?

Andrzej

Marius Mauch wrote:
On 02/12/04 Wazow wrote:


So now my situation is:

My initial gentoo installation was compiled with 2.4 kernel (and so
was my still used glibc). Then I upgraded to gentoo-dev-sources 2.6.1
and wondered why /usr/src/linux was not pointing to new kernel
sources. I thougth that it was a mistake and I have symlinked it to
2.6 sources. Now I should probably revert it back to 2.4.x sources,
shouldn't I?


No need to.


But I do not expect portage to detect that change, so basically it
will still ask for installing kernel-headers. Despite me having
installed 3 versions of complete gentoo-sources from 2.4.x... Why
these cannot be used?


kernel headers are installed separate from the kernel source tree in
/usr/include/linux


Is it safe just to inject header if my /usr/src/linux points to 2.4.22
sources? Where emerge will put this kernel headers?

Wouldn't it be more wise to recompile glibc for kernel 2.6 (or may be glibc needs to be ported to this new kernel headers first ? :) ).


Portage packages expect the kernel headers at /usr/include/linux, they
don't care if it's a symlink to a full kernel tree or a seperate copy of
the headers as provided by the linux-headers ebuild. However if you
change it it's best to recompile glibc followed by emerge -e world, so I
recommend to not touching it unnecessary. The most important thing: It
doesn't have to match the running kernel.

Marius



--
[EMAIL PROTECTED] mailing list



Reply via email to