similar to: [PATCH libguestfs] build: make autogen.sh update .git-module-status, as it should

My patch was wrong. I kept the sed transformation the same in the two places, but it wasn't strict enough to also work on the file contents. Sorry about that. This fixes it. >From 93927cc7b9f63c414e5bfeb7eba393fde3295601 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Fri, 20 Nov 2009 16:23:17 +0100 Subject: [PATCH libguestfs] build: correct sed

With the very latest git, "git submodule status" output may now start with a "+". This change makes it so that is also stripped away before comparing current and stored SHA1 values. >From 1bc2c5def80b8a0860a1980551d433f1fdce9a50 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Wed, 2 Dec 2009 15:06:48 +0100 Subject: [PATCH libguestfs]

Here's a patch series to make libguestfs use gnulib via a git submodule. The first thing I did was to look at the failures from "make syntax-check" and fix the config.h-related ones below. The others are now temporarily disabled via a variable in cfg.mk. I fixed the config-h problems and moved those change sets to precede the test-adding one, so that bisection still works, even if

This reinstates the autogen.sh-based test for the two required ocaml packages. I've tested it by running autoconf.sh first with neither of the two packages installed, then with only ocaml-xml-light installed. In both cases, autogen.sh failed as required. When both were installed, it worked as expected. >From 825d855b225c7c76371c72eae4d505a32c374007 Mon Sep 17 00:00:00 2001 From: Jim

The last patch was incomplete, since autoreconf must also be run with -f/--force. This change also updates the gnulib submodule to the latest, in order to pull in the progname change I made yesterday to give sensible names in diagnostics like this one: $ ./guestfish --version > /dev/full guestfish: write error: No space left on device Once the second change is pushed, you will have

In case you're ok with not version-controlling files imported via autogen, ... >From 72c829395bb6a4800516d4f535e18af48195585b Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Mon, 3 Aug 2009 11:00:22 -0400 Subject: [PATCH] Remove files imported via autogen.sh. * m4/.gitignore: Ignore these files. * m4/codeset.m4: Remove file. * m4/gettext.m4: Likewise. *

Only marginally useful, but some like it... This makes tests print "PASS" in green, and "FAIL" in red, when possible: The autogen.sh snippet ensures that this automake-1.11 feature is disabled when building-from-clone on a system with too-old automake. This *does* modify a source file (and a version-controlled one at that), but only when building from source on e.g. RHEL*

This used to be the case before commit 30de2cb603cd. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- README | 1 - autogen.sh | 5 +++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/README b/README index 679bf7010bbe..e5187a65ed47 100644 --- a/README +++ b/README @@ -107,7 +107,6 @@ Building and installing If you're cloning this from git the first

On Wed, Jun 16, 2010 at 03:38:22PM -0700, Dwayne Fontenot <dwayne.fontenot at att.net> wrote: > Is lib/ supposed to be empty in febootstrap git HEAD? Yes. Run ./autogen.sh to populate it with gnulib stuff. Actually, this may not work too well unless you have gnulib checked out exactly in ../gnulib. I need to ask Jim Meyering nicely if he'll make gnulib into a submodule of

There's a new syntax check rule from gnulib. It requires that you write e.g., exit (EXIT_SUCCESS), not exit (0). And the same for 1/EXIT_FAILURE and any other constants. There were a lot of violations, including a few false positives, so I started with the exemptions (see the .x-sc file below). Then I converted the vast majority automatically, with this: maint: use EXIT_SUCCESS and

>From 34af5f3be8b04443dc151e6d070aa49cbe59b7fc Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Fri, 20 Nov 2009 11:50:54 +0100 Subject: [PATCH libguestfs] maint: remove unnecessary include of openat.h * daemon/realpath.c: Don't include "openat.h". not used. --- daemon/realpath.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff

Well, just a simple helper. Signed-off-by: Axel Gembe <ago at bastart.eu.org> --- autogen.sh | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) create mode 100755 autogen.sh diff --git a/autogen.sh b/autogen.sh new file mode 100755 index 0000000..76a2462 --- /dev/null +++ b/autogen.sh @@ -0,0 +1,6 @@ +#!/bin/sh + +autoreconf -v --install -Wno-portability +libtoolize --copy

autogen.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 17d9a33cc29cf0ac5a08b528709baf4c49ee9b3b Author: Benjamin Otte <otte at gnome.org> Date: Mon Dec 3 16:45:40 2007 +0100 fix name of project diff --git a/autogen.sh b/autogen.sh index 04e60a1..39a9359 100755 --- a/autogen.sh +++ b/autogen.sh @@ -4,7 +4,7 @@ srcdir=`dirname $0` test -z

This allows the script to be run from somewhere other than the top-level build directory. --- autogen.sh | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/autogen.sh b/autogen.sh index 1a9a020..ab52ab6 100755 --- a/autogen.sh +++ b/autogen.sh @@ -2,6 +2,13 @@ # Run this to set up the build system: configure, makefiles, etc. # We trust that the user has a recent

Could someone add this autogen.sh script to the toplevel of openssh_cvs? Many projects include an autogen.sh script so that folks need not remember what auto commands need to get run and in what order. % cat autogen.sh #!/bin/sh # Run this program (./autogen.sh) after changing any of # the files that are used to automatically generate # other files. #aclocal autoheader autoconf #automake

Josh, Macports on OSX ships with automake-1.10 and the current autogen.sh detects 1.10 as an invalid version of automake. The following patch (snarfed from autogen.sh from libvorbis) fixes that. Once that is fixed there are still some other issues that need fixing for automake-1.10. Cheers, Erik diff -u -r1.16 autogen.sh --- autogen.sh 21 Nov 2006 01:40:57 -0000 1.16 +++ autogen.sh 10

if i run autogen.sh on fresh 1.1.beta9 source, it fails @ ./autogen.sh ... 100%[====================================>] 154,427 115.09K/s 08:45:56 (114.82 KB/s) - `wiki-export.tar.gz' saved [154427/154427] configure.in:16: required file `./config.rpath' not found configure.in:5: installing `./missing' configure.in:5: installing `./install-sh'

i have been playing around trying to get ice2 to work now for quite some time and frankly i am a bit frustrated by now... the anoying thing is how early in the whole proccess my problems actually start! running ./autogen.sh in the newest cvs version of ice2 results in <p>idoru:/usr/src/ices# ./autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it,

Hello, I couldn't help noticing that the debian build system in cvs was changed. As I used to compile and install from cvs, I discovered a small problem regarding autogen.sh. It's called in debian/rules, before the obj-dir is created (and changed into and ../configure is started). At least on my system autogen.sh implicitly runs ./configure, so the original source path is already

Hi Rich, Prompted by your "New commands to list devices by UUID and label" patch, I've adjusted it to use gnulib. While just compiling hash.[ch] is probably ok, in general (given the strict requirements of libguestfs) using the C files of a module is usually not an option, since you don't get the benefit of the module's m4 tests or automake snippets. For other modules,