On Fri, 2010-09-03 at 13:24 +0200, Balazs Scheidler wrote:

On Fri, 2010-09-03 at 06:09 +1200, chris packham wrote:

...

INSTALL is generated by the build process. If the build host has a different version of autotools then the contents of INSTALL can change which in turn causes problems for developers working from the git repository.

This patch removes the INSTALL file and adds it to .gitignore.

So, in your case autotools generates an INSTALL file? That's funny, this is not the same as the autotools generated one (in fact it is a bit outdated, but I wrote that to document how to install syslog-ng).

For me automake doesn't generate this file. Why does it for you?

autogen.sh contains:

aclocal sed -i -e 's/PKG_PROG_PKG_CONFIG(\[0\.16\])/PKG_PROG_PKG_CONFIG([0.14])/g' aclocal.m4

autoheader automake --foreign --add-missing autoconf

as I understand automake will only be adding the INSTALL file if it doesn't exist. Are you using -f for automake?

Actually our problem might be this $(call MESSAGE,"Running autogen.sh") $(Q)cd $(SYSLOG_NG_GIT_DIR) && $(AUTORECONF) 2> /dev/null $(Q)touch $@ So we're lying to our developers for a start. If I do run autogen.sh instead I get this error configure.in:513: warning: macro `AM_PATH_GLIB_2_0' not found in library configure.in:513: error: possibly undefined macro: AM_PATH_GLIB_2_0 which is probably the reason we didn't just use autogen.sh in the first place. Looking at the expanded $(AUTORECONF) it expands to "/usr/bin/autoreconf -f -i" (plus a lot of environment vars for our cross-compile environment). I'll try fiddling with these options to see if some of them changes the behaviour.