]> git.ipfire.org Git - thirdparty/libvirt.git/commit
build: don't ship access syms files in tarball
authorEric Blake <eblake@redhat.com>
Tue, 2 Jul 2013 16:28:20 +0000 (10:28 -0600)
committerEric Blake <eblake@redhat.com>
Tue, 2 Jul 2013 17:49:32 +0000 (11:49 -0600)
commit336bf8e28bdd6ee34453d6acdaf9f7a790f0d3c4
tree7edeef419a09db44b778f0788a0dd77b5037f09c
parent1165e39ca3a5fe97135a74d4a9d8ef78038ad484
build: don't ship access syms files in tarball

On a mingw VPATH build (such as done by ./autobuild.sh), the tarball
created by 'make dist' was including generated files.  The VPATH
rules were then seeing that the tarball files were up-to-date, and
not regenerating files locally, leading to this failure:

  GEN      libvirt.syms
cat: libvirt_access.syms: No such file or directory
cat: libvirt_access_qemu.syms: No such file or directory
cat: libvirt_access_lxc.syms: No such file or directory
make: *** [libvirt.syms] Error 1

We already have a category for generated sym files, which are
intentionally not part of the tarball; stick the access sym
files in that category.  The rearrange the declarations a bit
to make it harder to repeat the problem, dropping things that
are now redundant (for example, BUILT_FILES already includes
GENERATED_SYM_FILES, so it does not also need to call out
ACCESS_DRIVER_SYM_FILES).

* src/Makefile.am (USED_SYM_FILES): Don't include generated files.
(GENERATED_SYM_FILES): Access syms files are generated.
(libvirt.syms): Include access syms files here.
(ACCESS_DRIVER_SYMFILES): Rename...
(ACCESS_DRIVER_SYM_FILES): ...for consistency.

Signed-off-by: Eric Blake <eblake@redhat.com>
src/Makefile.am