Yep, 2.6.27 is ancient now ;-)

[Steve Dover]

Mike Frysinger wrote:
> On Monday, February 17, 2014 08:39:51 Christopher Meng wrote:
>> Because we don't use uclibc.
>
> what is this "we" business ?  lots of people use uClibc, and that isn't the
> problem here.  in fact, building 2013.62 w/uClibc works just fine for me.
>
> the problem is that Steve's kernel headers are broken.  he didn't say what
> version he's using, but i'm guessing ancient considering that header was fixed
> in the 2.6.29 release to include linux/types.h correctly.
> -mike
>

I am working with 2.6.27.*, because I am targeting ancient devices
that are still being used.  And apparently that 'fix' was not backported
to 2.6.27 for long term support.

Note: as of this writing, 2.6.27 is no longer considered long-term,
and 2.6.32 is still, as of this writing considered a long-term kernel.

Bottom line, my fix works, or I could patch the kernel source.
Have not decided which way to go because I am not delivering a kernel,
I am just compiling against a known set of kernel headers.

So, for now, we just need to note that 2013.62 needs at least 2.6.29
kernel headers to build without error, otherwise if you are using
an older kernel, you need the patch.