Hi,
I’d like to follow up on this issue. According to the libc bug reporting
guidelines, one should hear from the Debian maintainers whether the bug
could possibly be Debian-specific before reporting them upstream. Can
you comment on that?
The bug might look like it is a weird corner case, but it
Author: ps-guest
Date: 2010-05-14 11:47:01 + (Fri, 14 May 2010)
New Revision: 4267
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/patches/kfreebsd/local-sysdeps.diff
Log:
* kfreebsd/local-sysdeps.diff: update to revision 3038 (from glibc-bsd).
Closes: #58
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 581545 + pending
Bug #581545 [libc0.1-dev] [kfreebsd] netinet/in.h origin issue
Bug #581546 [libc0.1-dev] [kfreebsd] netinet/in.h origin issue
Added tag(s) pending.
Fri, 14 May 2010 13:08:18 +0200 (CEST)
Petr Salinger wrote:
> > There are defined some kernel-specific macroses, e.g.
> > IPPROTO_DIVERT, and some FreeBSD software expect to find it there.
> >
> > But on Debian this header provided by libc, not
> > kfreebsd-kernel-header. And this header could on
There are defined some kernel-specific macroses, e.g. IPPROTO_DIVERT,
and some FreeBSD software expect to find it there.
But on Debian this header provided by libc, not kfreebsd-kernel-header.
And this header could only been found in kfreebsd-headers-$(version)
which makes difficult to build-depe
5 matches
Mail list logo