Re: Bug#630206: libnss-myhostname: FTBFS: fatal error: asm/types.h: No such file or directory
On Sun, 12.06.11 21:35, Joachim Breitner (nomeata@debian.org) wrote:
> Hi Christoph, Hello Lennart,
>
> Am Sonntag, den 12.06.2011, 12:34 +0200 schrieb Christoph Egger:
> > Package: src:libnss-myhostname
> > Version: 0.3-1
> > Severity: serious
> > Tags: sid wheezy
> > Justification: fails to build from source (but built successfully in the past)
> >
> > Hi!
> >
> > Your pacage failed to build on the kfreebsd-* buildds:
> > libtool: compile: x86_64-kfreebsd-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/build/buildd-libnss-myhostname_0.3-1-kfreebsd-amd64-oyrjWQ/libnss-myhostname-0.3 -include ./config.h -Wall -g -O2 -Wall -W -Wextra -pedantic -pipe -Wformat -Wold-style-definition -Wdeclaration-after-statement -Wfloat-equal -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wshadow -Wendif-labels -Wpointer-arith -Wcast-align -Wwrite-strings -Winline -Wno-unused-parameter -ffast-math -fvisibility=hidden -fdiagnostics-show-option -MT netlink.lo -MD -MP -MF .deps/netlink.Tpo -c /build/buildd-libnss-myhostname_0.3-1-kfreebsd-amd64-oyrjWQ/libnss-myhostname-0.3/netlink.c -fPIC -DPIC -o .libs/netlink.o
> > /build/buildd-libnss-myhostname_0.3-1-kfreebsd-amd64-oyrjWQ/libnss-myhostname-0.3/netlink.c:25:23: fatal error: asm/types.h: No such file or directory
> > compilation terminated.
> > make[3]: *** [netlink.lo] Error 1
> >
> > Full build log at
> > https://buildd.debian.org/status/fetch.php?pkg=libnss-myhostname&arch=kfreebsd-amd64&ver=0.3-1&stamp=1307742167
> >
> > If you have further questions please mail debian-bsd@lists.debian.org
>
>
> it seems that nss-myhostname has changed the way it acquires link
> addresses between versions 0.2 to 0.3 to make use of the netlink
> interface. This breaks the package on hurd and freebsd kernels. What
> should we do here? I see three options:
I think it is a major waste of time thinking about BSD and Hurd.
That said, I'd be willing to merge a patch that adds support for those
legacy systems -- if it is minimal. Note however that it wouldn't be
release critical to me, i.e. I will not care if it works or not when
releasing a new version. But I geuss that doesn't matter much since it
is quite a finished project and I expect very few updates in the future.
So yupp, if you send me a minimal, non-intrusive patch with proper
coding style that does not pollute the Linux code I'd be willing to
merge it.
The emphasis is on non-intrusive minimalism.
> B. Ask Lennart to try to make his program portable.
Nah, I will not work on this. Netlink is Linux specific -- it cannot be
made on the legacy kernels, and I don't care for the legacy kernels
anyway and won't spend time on them.
Lennart
--
Lennart Poettering - Red Hat, Inc.
Reply to: