]> git.ipfire.org Git - thirdparty/libvirt.git/commit
build: silence libtool warning on probes.o
authorEric Blake <eblake@redhat.com>
Fri, 25 May 2012 15:57:56 +0000 (09:57 -0600)
committerEric Blake <eblake@redhat.com>
Fri, 25 May 2012 18:00:05 +0000 (12:00 -0600)
commit0159295d29d9688e71dcfd7829914ae817b547dc
tree23e1a909fbfe3172affe3b68ed40cf4162ff14d3
parent4878a33125a0793b8af3a1f9837bb1c396a80420
build: silence libtool warning on probes.o

Libtool supports linking directly against .o files on some platforms
(such as Linux), which happens to be the only place where we are
actually doing that (for the dtrace-generated probes.o files).  However,
it raises a big stink about the non-portability, even though we don't
attempt it on platforms where it would actually fail:

  CCLD   libvirt_driver_qemu.la

*** Warning: Linking the shared library libvirt_driver_qemu.la against
the non-libtool
*** objects  libvirt_qemu_probes.o is not portable!

This shuts libtool up by creating a proper .lo file that matches
what libtool normally expects.

* src/Makefile.am (%_probes.lo): New rule.
(libvirt_probes.stp, libvirt_qemu_probes.stp): Simplify into...
(%_probes.stp): ...shorter rule.
(CLEANFILES): Clean new .lo files.
(libvirt_la_BUILT_LIBADD, libvirt_driver_qemu_la_LIBADD)
(libvirt_lxc_LDADD, virt_aa_helper_LDADD): Link against .lo file.
* tests/Makefile.am (PROBES_O, qemu_LDADDS): Likewise.
src/Makefile.am
tests/Makefile.am