Bug#220624: libc6-dev: breaks builds on 2.4 systems because depending on linux-kernel-headers which contain 2.5 headers

[Alex Tsariounov <alext@fc.hp.com>]

On Thu, 2003-11-13 at 12:40, Daniel Jacobowitz wrote:
> On Thu, Nov 13, 2003 at 12:37:19PM -0700, Alex Tsariounov wrote:
> > I see.  But it worked fine on versions before the ds1-* releases.  I.e.,
> > it worked on the libc6-dev-2.3.2-9 release (I think that was without the
> > linux-kernel-headers package).   With the recent upgrade, it breaks.
> 
> The reason you're supposed to copy these headers is so that it doesn't
> break when this happens.

Well, I've always considered doing this type of stuff somewhat of a
hack: how many copies of various headers do I need to keep around? 
However, I think we're in philosophical territory here.  

The thing is, if query_module() is a public libc function, and I assume
it is since it's listed in section 2 of man, then there should be an
include file that I can include that facilitates the interface of this
function, and that include file needs to be specified in the function's
man page.

In fact the query_module() man page does specify the linux/module.h as
the appropriate header file to include.  

This should be the same for any libc function, whether printf() for
which according to it's man page you should include stdio.h, or
query_module for which you include linux/module.h.

Thanks,
Alex