Bug#301641: Linux kernel include files still inconsistent on sarge

[Horms <horms@verge.net.au>]

On Thu, Mar 31, 2005 at 05:16:55PM +0200, Joerg Schilling wrote:
> Horms <horms@debian.org> wrote:
> 
> > > When compiling star, I get error messages like:
> > > 
> > >         =3D=3D> COMPILING "fflags.o"
> > > In file included from /usr/include/linux/ext2_fs.h:20,
> > >                  from fflags.c:41:
> > > /usr/include/linux/ext2_fs_sb.h:48: error: parse error before "u32"
> > > /usr/include/linux/ext2_fs_sb.h:50: error: parse error before '*' token
> > > /usr/include/linux/ext2_fs_sb.h:55: error: parse error before '}' token
> > > 
> > > They are caused by the fact that data structures that are needed=20
> > > for user space applications still base on inofficial types defined
> > > only in case you are compiling a linux kernel.
> > > 
> > > It is impossible to compile star using official methods (adding
> > > other include files that are allowed to be included by user space program=
> > > s).
> > > 
> > > The related problem has been reported to the linux kernel developers
> > > more than 2. years ago. Is there any help that the Linux kernel
> > > will be fixed in the near future?
> >
> > I would suggest making a patch for your proposed cleanup of
> > these types and submitting it both upstream and here.
> 
> I could easily make a patch for one or two files I am depending directly on.
> THe problem is that the linus kernel include files suffer from a major 
> missconception that could only be cured in case the Linux Kernel developers
> would do it for now and the future.

That may be so, but if you want this fixed it seems that
you would be the perfect person to start the discussion,
and a good way to do that is to produce some patches.

-- 
Horms