similar to: [LLVMdev] make dist?

Hi Tanya, The first thing you need to understand is that there are multiple make targets to support this feature. I'll briefly describe each here so you have an overview and then delve into the details later. * distdir - builds the distribution directory from which the distribution will be packaged * dist - builds each of the distribution tarballs (tar.gz,

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

On Mon, Oct 05, 2015 at 06:12:03PM +0300, Roman Kagan wrote: > On Mon, Oct 05, 2015 at 02:17:52PM +0100, Richard W.M. Jones wrote: > > On Mon, Oct 05, 2015 at 03:40:01PM +0300, Roman Kagan wrote: > > > -guestsdir="$(cd ../tests/guests && pwd)" > > > -f="$guestsdir/windows.img" > > > +abs_top_builddir="$(cd ..; pwd)" >

Hi, > I hope this brief tutorial has helped. Feel free to ask questions. > Further details can be found in Makefile.rules. Although I don't think it uses automake, chapter 13 of http://sources.redhat.com/autobook/autobook/autobook_toc.html may still be useful since it gives a similar overview. Cheers, Ralph.

modified ovirt-node-image for inclusion in Fedora Removes ovirt-node-image-pxe sub package adds get-ovirt-node-image script adds generate-ovirt-node-pxe-tree script (replaces subpackage) moved all the scripts/tools into tools subdir adds new rpm, ovirt-node-recipe includes tools, manifests, and ks file/recipe Process for building upstream ovirt node packages.... 1. Build ovir-node.rpm in koji

Another test, the same as before.

Best of .. 4?

After enabling procmail debugging ...

This is a repost so I can test my procmail script / automatic testing framework. The patch series is identical to v1. Rich.

Patch 1 cleans up the gobject tests. Patches 2 and 3 remote gtk-doc, which is slow and useless, and replace it with a simple manual page. https://bugzilla.redhat.com/show_bug.cgi?id=1465665 Rich.

Reid, First, thanks for the excellent overview. This seems like it will be very useful. I have a question about dist-check. You mention that it will triple the amount of disk space I am using. I am guessing its because it does the following: > 11. runs make dist > 12. runs make clean > 13. runs make dist-clean It it necessary for dist-check to run make dist? Why would we

On Tue, 2006-04-11 at 21:03 -0500, Tanya Lattner wrote: > Reid, > > First, thanks for the excellent overview. This seems like it will be very > useful. > > I have a question about dist-check. > > You mention that it will triple the amount of disk space I am using. I am > guessing its because it does the following: > > 11. runs make dist > > 12.

Otherwise, automake will fail to process vivified/code/Makefile.am --- configure.ac | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index a3e186b..0e28374 100644 --- a/configure.ac +++ b/configure.ac @@ -300,6 +300,7 @@ else AC_MSG_NOTICE([Vivified was not enabled.]) fi AM_CONDITIONAL(HAVE_VIVI, [test "x$HAVE_VIVI" = xyes])

Without this option, configure will fail when there is no display. Signed-off-by: Masami HIRATA <msmhrt at gmail.com> --- configure.ac | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configure.ac b/configure.ac index de8a064..61d6f69 100644 --- a/configure.ac +++ b/configure.ac @@ -593,16 +593,16 @@ working. AC_MSG_FAILURE([$QEMU version must be >=

Hi Reid, > On Tue, 2006-04-11 at 21:03 -0500, Tanya Lattner wrote: > > It it necessary for dist-check to run make dist? > > Y'know, when I typed that, I knew you were going to ask that. It > doesn't make sense to me either. Seems a bit overkillish to me. I think a `make distcheck' should do a `make dist' because it checks that a tarball can reproduce itself.

All, We've accumulated quite a few changes to libvorbis since the 1.2.0 release. I'd like to do a new one, a propose that 1.2.1 happen May 5 or so. So, if you have any outstanding issues, please mention them here, and please check that current svn is working for you. Thanks, -r

We are migrating to Weblate (the Fedora instance, in particular) for translations instead of Zanata. Adapt our tooling a bit to the different workflow: - Weblate takes care of updating the po files whenever a new translation catalog is available, so stop doing that on our own: this meant also tweaking the po4a usage for POD documentations, resulting in simpler rules (IMHO) - ensure that the

I have committed changes to Makefile.rules (and others) that will assist in building releases or distributions. The new "dist" target will first perform a "make check" to ensure that all the software builds and that basic sanity checks pass (none have been implemented). If that succeeds, then the directory structure is traversed again for the "distdir" target which

This patch series modernizes various aspects of the autotools based build system. There is a lot more that could and should be done, but I tried to stay conservative for now and just resolve some of the most obvious issues. Max Horn (5): configure: replace XIPH_C_FIND_ENDIAN by AC_C_BIGENDIAN autogen.sh: replace this by a simple call to autoreconf configure: always print

Carrying on this conversation: http://lists.tartarus.org/pipermail/xapian-discuss/2007-March/003513.html void TermGenerator::set_stopper(stopper) Stopper * stopper CODE: // FIXME: no corresponding SvREFCNT_dec(), but a leak seems better than // a SEGV! SvREFCNT_inc(ST(1)); THIS->set_stopper(stopper); It would be good to fix these FIXMEs. A class-level HASH could be