Looking at /usr/include/fam.h (the only FAM header file), it appears to
provide a pure C interface only. The library has an awful lot of C++
symbols, but it seems clear that nobody's supposed to be linking to them.
Changing the name is reasonable anyway, but it looks like it might be safe
for it
>a) libkpathsea: It has a new soname, and I have not checked at all
> whether this causes problems in compiling other packages.
This means libkpathsea3 will no longer be available in unstable, right?
I have attempted to check whether this could cause any trouble in transitions
to testing (by l
libgc, apt, fam, and goodness knows what else FBTFS due to this bug -- which
is a trivial header error -- but only on ia64.
It's not clear what the right course of action is. If the "old" glibc in sid
builds cleanly with gcc 4.0, almost certainly it should be uploaded with a
fix for bug 318429
3 matches
Mail list logo
