[sllug-members]: libc question

[Joe George]

On Tue, Jan 20, 2009 at 9:19 AM, Thomas S Hatch <thatch45 at gmail.com> wrote:
> Thats what I thought, I am just getting strange compile errors and thought
> it was worth checking.  I am trying to cross compile some code for an arm 7
> chip, I think that something is wrong with my arm toolchain, I will ask
> again when I have more info on it.
>
> On Tue, Jan 20, 2009 at 9:02 AM, Stuart Jansen <sjansen at buscaluz.org> wrote:
>>
>> On Tue, 2009-01-20 at 08:52 -0700, Thomas S Hatch wrote:
>> > So, correct me if I am wrong, but if I have a driver that has been
>> > made for the 2.4.21 kernel, and I am building it against the 2.4.21
>> > kernel, then I need a compatible version of glibc and gcc.  Other wise
>> > I cannot build against a 4.2.21 kernel with gcc 4.3.  If this is not
>> > clear just say so.
>>
>> I'm sure you've already read that none of the libc functionality can be
>> be by kernel code, but I'll repeat it to make sure we're on the same
>> page. (Although the kernel does include rough equivalents for some libc
>> functions.)
>>
>> While the internals of the kernel are constantly changing, great pains
>> are taken to make sure that the external API & ABI stays the same. You
>> _should_ be able to use an old libc with a new kernel, you just won't be
>> able to take advantage of new kernel features supported by later
>> versions of libc.
>>

Is there a reason you need to use such an ancient kernel?  If you can change,
you could use buildroot.org which is well supported for ARM.

Joe