... you may get a link failure until you run the following command: make -C v2v link.sh Rich. PS: Can someone explain why: $ pkg-config --libs libvirt -lvirt -ldl -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic ? -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
On Tuesday 26 August 2014 23:02:31 Richard W.M. Jones wrote:> ... you may get a link failure until you run the following command: > > make -C v2v link.shIn such case, touch'ing configure.ac will cause configure to be rerun and thus v2v/Makefile to be updated.> PS: Can someone explain why: > > $ pkg-config --libs libvirt > -lvirt -ldl -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions > -fstack-protector-strong --param=ssp-buffer-size=4 > -grecord-gcc-switches -m64 -mtune=genericDouble bug here: CFLAGS shouldn't be in LDFLAGS, and those CFLAGS surely aren't required when linking libvirt... -- Pino Toscano
On Tue, Aug 26, 2014 at 11:02:31PM +0100, Richard W.M. Jones wrote:> > ... you may get a link failure until you run the following command: > > make -C v2v link.sh > > Rich. > > PS: Can someone explain why: > > $ pkg-config --libs libvirt > -lvirt -ldl -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=genericEwww, that's a bug. Libvirt should not be leaking any of those compiler flags to the pkg-config file. It should have -lvirt at most Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|