[libvirt] [PATCH] python: Fix makefile rule for code generation

2011-07-21 Thread Matthias Bolte
Commit 8665f85523f0451c changed generated.stamp to $(GENERATE).stamp, but missed one instance in the CLEANFILES list. This can break the build in case the generated code is deleted but the .stamp file stays around and therefore the code isn't regenerated. --- python/Makefile.am |2 +- 1 files

Re: [libvirt] [PATCH] python: Fix makefile rule for code generation

2011-07-21 Thread Daniel P. Berrange
On Thu, Jul 21, 2011 at 01:47:14PM +0200, Matthias Bolte wrote: Commit 8665f85523f0451c changed generated.stamp to $(GENERATE).stamp, but missed one instance in the CLEANFILES list. This can break the build in case the generated code is deleted but the .stamp file stays around and therefore

Re: [libvirt] [PATCH] python: Fix makefile rule for code generation

2011-07-21 Thread Matthias Bolte
2011/7/21 Daniel P. Berrange berra...@redhat.com: On Thu, Jul 21, 2011 at 01:47:14PM +0200, Matthias Bolte wrote: Commit 8665f85523f0451c changed generated.stamp to $(GENERATE).stamp, but missed one instance in the CLEANFILES list. This can break the build in case the generated code is deleted