Is there a list of which kernel versions (are supposed to) work with (each version of) klibc? I do recall reading something that said klibc should run under any version of the kernel, regardless of which version it is compiled against. Following the new instructions on this list earlier (to use the KLIBCKERNELSRC= parameter to point to the installed kernel headers) as well as also making the symlink "linux" (pointing to same header tree), I find that only more recent kernels work with klibc. I am trying to determine just how far back in kernel versions I can go, so I know what work I will have to do to bring some (older) kernel patches to recent kernels. Fortunately, early user space will let me abandon a couple of those patches. Klibc 1.5.{16,17,18} only compile with kernels since 2.6.32. But the real issue is actually running. If Linux changed syscall interfaces such that these version combinations won't even run under older kernels, then I need to either bring all my kernel patches up to date sooner (where I had hoped to spend the time either doing them over or finding a way to abandon them), or try to figure out how to get Klibc to compile with an older kernel (doesn't have to be the latest Klibc, but even older versions of Klibc were running into "header hell" with older kernels). Even a list of which versions of Linux were used with each version of Klibc in the past might help. I tried to use the kernel versions dated just before each past Klibc release (of 1.5.X versions, only), but those other various other errors.
Gilles Espinasse
2010-Jul-20 12:55 UTC
[klibc] a list of which kernel versions work with klibc
----- "Phil Howard" <kunnskaperen at gmail.com> a ?crit :> Is there a list of which kernel versions (are supposed to) work with > (each version of) klibc? >1.5.15 work with 2.6.27.x http://ipcop.svn.sourceforge.net/viewvc/ipcop/ipcop/trunk/lfs/klibc?revision=3106&view=markup we have used 1.5.10 with 2.6.25.x Gilles
On Tue, Jul 20, 2010 at 8:55 AM, Gilles Espinasse <g.esp at free.fr> wrote:> > ----- "Phil Howard" <kunnskaperen at gmail.com> a ?crit : > >> Is there a list of which kernel versions (are supposed to) work with >> (each version of) klibc? >> > 1.5.15 work with 2.6.27.x > http://ipcop.svn.sourceforge.net/viewvc/ipcop/ipcop/trunk/lfs/klibc?revision=3106&view=markupThen I guess I could focus on why that combination fails for me: http://phil.ipal.org/linux-and-klibc/2010-07-21/klibc-linux-combo-log/000324-klibc-1.5.15-linux-2.6.27.48-i686.log http://phil.ipal.org/linux-and-klibc/2010-07-21/klibc-linux-combo-log/000324-klibc-1.5.15-linux-2.6.27.48-x86_64.log Here is the latest script. It uses both the "linux" symlink (there is an "ln" command seen in the logs making the symlink), and the KLIBCKERNELSRC= parameter on the make command. I hope I have them pointing in the right place. Some combinations (e.g. 1.5.16 through 1.5.18 with more recent kernels) do work, which suggests something is right in my script. In the above logs, it shows an error where "linux/limits.h" is now found. Yet there is "linux/limits.h" relative to the header install target, as shown its md5 checksum before compilation was started. Something went wrong somewhere. Originally I posted to just see if there was existing knowledge of such problems. But if this pairing works for you, that means at least something is different between how you ran it, and how I did. I ran it by that script. The script is at: http://phil.ipal.org/linux-and-klibc/2010-07-21/compile-klibc> we have used 1.5.10 with 2.6.25.xResults of that pairing will be in the same directory as the above ones, later on. Anyway, I guess it might be time for me to dig into the builds, Makefiles, and source trees, to see what went wrong.