bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libvirt] Linker error in gnulib test-binary-io.c


From: Eric Blake
Subject: Re: [libvirt] Linker error in gnulib test-binary-io.c
Date: Wed, 18 Jul 2012 15:13:47 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

On 06/17/2012 03:46 AM, Matthias Bolte wrote:
> I get the following error on Ubuntu 11.04 with current libvirt git HEAD:
> 
> $ make check
> [...]
>   CC     test-binary-io.o
> test-binary-io.c: In function 'main':
> test-binary-io.c:54:7: warning: implicit declaration of function
> 'set_binary_mode'

Known pitfall of incremental development, and I think it happens if you
build libvirt.git prior to libvirt commit e925ea31 (although I could be
wrong, maybe libvirt commit db835b7 was the culprit), then do an
incremental update.  What happens is that prior to the problem point,
gnulib-tool was installing binary-io.h in the test directory, as it was
a dependency for tests but not for files used directly by libvirt.
After the problem point, one of our gnulib updates picked up some
dependency changes that graduated binary-io.h into our normal include
space, for use as part of libvirt (or at least as part of the gnulib
modules compiled directly into libvirt and not just the testsuite).
Meanwhile, version skew between the two versions of binary-io.h mean
that if you pick up the wrong version, you get a compilation failure.

Nuke the file in gnulib/tests/ to proceed.  That can be done with a
clean build, rather than an incremental build.

I'm cc'ing bug-gnulib, though, in case there is a way to make
'gnulib-tool --update' (and/or ./bootstrap) remove old files from the
tests directory once they have been graduated into the main directory as
a result of some other module dependency change.

-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]