Re: Bug#2697: symlink /usr/include/asm in libc5-dev
> It depends on how xntp was broken. If it used a kernel interface that
> changed, then yes, it would have to be updated accordingly. However,
FYI, it was infact a *semantic* change to a kernel interface (the raw
interface itself didn't change, it was what happened when you'd
already bound a specific vs. generic address on a socket.) Nothing to
be done for it except change xntpd sources... the problem make was
similar.
In any case -- it would be good if the package libc5-dev package had
some hint as to *which* kernel headers it included... Perhaps not as
far as a dependency check against image, but just a note in the
description. (The whole kernel/libc skew issue is complicated, but the
one thing that *any* approach needs is enough information that one can
figure out afterwards what happenned :-)
Reply to: