Fwd: Please backport a patch to branches/uClibc_0_9_30

Kyle Sallee kyle.sallee at gmail.com
Sun May 10 00:37:28 UTC 2009


I probably should have replied to the list.


---------- Forwarded message ----------
From: Kyle Sallee <kyle.sallee at gmail.com>
Date: Sat, May 9, 2009 at 5:36 PM
Subject: Re: Please backport a patch to branches/uClibc_0_9_30
To: rhabarber1848 <rhabarber1848 at web.de>


Headers from linux kernel 2.6.29.2 can be used.
At least I compiled uClibc using 2.6.29.1 kernel headers.
After untarring the source I ran
make headers_install
then I copied the headers from usr/include/*
to where I wanted them.
I have linux kernel headers both in /usr/include/
and in /opt/uClibc/usr/include/
which I am currently using for my uClibc cross compile toolchain.



On Sat, May 9, 2009 at 4:08 PM, rhabarber1848 <rhabarber1848 at web.de> wrote:
> Mike Frysinger wrote:
>
>> older versions of linux headers werent as sanitized as they could (should)
>> be,
>> nor were there efforts to address it.  so there have been some hacks added
>> to
>> the C library to workaround it.  the linux kernel has long since addressed
>> this kind of thing by adding mechanisms to clean and install the headers.
>
> Hi,
>
> I solved the problem by using
> http://launchpadlibrarian.net/3370483/linux-kernel-headers_2.6.17.orig.tar.gz
> because I need to use kernel 2.6.17 in my case.
> With those headers, provided by Ubuntu, everything works well.
> Thanks for you help.
>
> Cheers, rhabarber1848
>
>
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://lists.busybox.net/mailman/listinfo/uclibc
>


More information about the uClibc mailing list