there seems to be an incompatibility to the last glibc due to .
Eventually this breaks gnulib unittests (and maybe more).
Debugging went from an assert, to bidngin different symbols, to changed function names to different header resolution.
Because it expects it to behave "posixly" but arguments are changed differently.
# get and build latest libvirt to get the local gnulib
$ wget http://
$ tar xf libvirt-
$ cd libvirt
$ apt build-dep libvirt
$ make -j4
You can run the following simplified test derived from the unit test (it is much shorter, so easier to debug e.g. in -E).
$ cat << EOF >> test1.c
int main (void)
$ gcc -I ./gnulib/lib -I . test1.c -H
You can see in -H output already the difference in the paths of the headers that it uses:
If you build with -E you'll also see that it now uses getopt from glibc instead of the prefixed rpl_getopt from gnulib.
It behaves as if it would not find gnulib and instead fall back to glibc. But it finds gnulib, instead due to glibc's changes its implementation is fetched before and due to that pulling in glibc's behavior while the unit test is verifying against the one it expects from gnulib.
Sorry, but I don't see the right fix here yet - I could easily silence the test but that is no fix. Especially if there might be implications due to handling the args (slightly) differently.
I really wanted to come up with the same test against gnulib alone, but I was lost in the build system for too long and could not get the example to fail without libvirt (OTOH I'm sure it would).
Therefore I'm reaching out to you for your help and experience on the build system what could be done.