Re: [kfreebsd] netinet/in.h origin issue
- To: Petr Salinger <Petr.Salinger@seznam.cz>
- Cc: firstname.lastname@example.org, email@example.com
- Subject: Re: [kfreebsd] netinet/in.h origin issue
- From: Alexander GQ Gerasiov <firstname.lastname@example.org>
- Date: Fri, 14 May 2010 15:02:21 +0400
- Message-id: <email@example.com>
- In-reply-to: <Pine.LNX.firstname.lastname@example.org>
- References: <email@example.com> <Pine.LNX.firstname.lastname@example.org>
Fri, 14 May 2010 13:08:18 +0200 (CEST)
Petr Salinger <Petr.Salinger@seznam.cz> 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 only been found in
> > kfreebsd-headers-$(version) which makes difficult to build-depend
> > on it.
> > I think this should be fixed some way to allow IPPROTO_DIVERT usage
> > in correct way without hacks in sources.
> Please, could you verify whether adding line
> #define IPPROTO_DIVERT 258 /*
> divert pseudo-protocol */
> into /usr/include/bits/in.h fixes all your needs ?
Yes, but are you sure this is a correct fix for this issue?
Do you suggests to track FreeBSD kernel's netinet/in.h and append
everything missed in libc's netinet/in.h to bits/in.h?
This may be correct from tecnical point of view, but from organization
one this will be a headache to keep them synchronized. I think that
freebsd code should be brought to system with freebsd-kernel-headers,
but you know this better, of course.
Alexander GQ Gerasiov
e-mail: email@example.com Jabber: firstname.lastname@example.org
Homepage: http://gq.net.ru ICQ: 7272757
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1