AM_CONDITIONAL() statements can't be conditionally executed (automake

2002-03-12  James Henstridge  <james@daa.com.au>

	* acinclude.m4 (LIBGTOP_HEACKER_TESTS): AM_CONDITIONAL()
	statements can't be conditionally executed (automake compat fix).
	(GNOME_LIBGTOP_SYSDEPS): move the conditional here so that it is
	always executed.

2002-03-12  James Henstridge  <james@daa.com.au>

	* Makefile.am (MAKEINFO): using += seems to screw up the build
	with newer automakes.  Set it explicitly (using @MAKEINFO@) seems
	to be compatible with both.
This commit is contained in:
James Henstridge
2002-03-12 14:57:12 +00:00
committed by James Henstridge
parent 1c248d7e93
commit 4df359b9d3
4 changed files with 19 additions and 5 deletions

View File

@@ -1,3 +1,9 @@
2002-03-12 James Henstridge <james@daa.com.au>
* Makefile.am (MAKEINFO): using += seems to screw up the build
with newer automakes. Set it explicitly (using @MAKEINFO@) seems
to be compatible with both.
2001-11-26 Abel Cheung <maddog@linux.org.hk>
* libgtop.texi, Makefile.am: Renamed to libgtop2.texi

View File

@@ -4,7 +4,7 @@ libgtop2_TEXINFOS = libgtop2.texi about.texi reference.texi \
auto-macros.texi version.texi main.texi \
white-paper.texi
MAKEINFO += -I @libgtop_top_builddir@/doc
MAKEINFO = @MAKEINFO@ -I @libgtop_top_builddir@/doc
EXTRA_DIST = auto-macros.texi.in