Re: Difference between AM_CFLAGS, AM_CPPFLAGS, and AM_LDFLAGS

2002-09-09 Thread Paul Smith
%% Stephen Torri <[EMAIL PROTECTED]> writes: st> On Mon, 2002-09-09 at 23:11, Steve M. Robbins wrote: >> On Mon, Sep 09, 2002 at 10:33:40PM -0500, Stephen Torri wrote: >> > AM_CFLAGS - compile time flags >> > AM_CPPFLAGS - preprocessor flags (e.g. -I, -D) >> > AM_LDFLAGS - linker flags

Re: Difference between AM_CFLAGS, AM_CPPFLAGS, and AM_LDFLAGS

2002-09-09 Thread Stephen Torri
On Mon, 2002-09-09 at 23:11, Steve M. Robbins wrote: > On Mon, Sep 09, 2002 at 10:33:40PM -0500, Stephen Torri wrote: > > I am just posting this to make sure I understand the difference between > > these: > > > > AM_CFLAGS - compile time flags > > AM_CPPFLAGS - preprocessor flags (e.g. -I, -D) >

Difference between AM_CFLAGS, AM_CPPFLAGS, and AM_LDFLAGS

2002-09-09 Thread Stephen Torri
I am just posting this to make sure I understand the difference between these: AM_CFLAGS - compile time flags AM_CPPFLAGS - preprocessor flags (e.g. -I, -D) AM_LDFLAGS - linker flags (e.g. -L) I am working on a project that is updating its Makefile.am files. I see a variety of flags in one varia

Releasing Autoconf 2.54

2002-09-09 Thread Akim Demaille
If anybody sees a good reason to hold the release, please speak up now!

Re: GNU packs with generated README

2002-09-09 Thread Eric Siegerman
On Fri, Sep 06, 2002 at 01:37:57PM +0200, Ronald Landheer wrote: > What I'd like to know is whether it is possible to keep the GNU (--gnu) > standards for Automake's checking, but not have it look at README while > bootstrapping [because README is a generated file, and doesn't exist > yet at tha

Re: ac_config_libobj_dir broken

2002-09-09 Thread Akim Demaille
| Index: ChangeLog | from Akim Demaille <[EMAIL PROTECTED]> | | * lib/autoconf/functions.m4 (AC_FUNC_GETLOADAVG): Use $srcdir when | looking for a replacement file. | * lib/autoconf/general.m4 (AC_CHECK_DECLS): Check that the | directory is relative. | * doc/autoc

Re: GNU packs with generated README

2002-09-09 Thread Akim Demaille
> "Ronald" == Ronald Landheer <[EMAIL PROTECTED]> writes: >> Please, promote autoreconf use for bootstrapping. That way, we >> will be reported more cases, more bugs etc. which is always a good >> thing. In addition, in the future, if we add new people in the >> build system (such as the re

RE: GNU packs with generated README

2002-09-09 Thread Ronald Landheer
In response to both Tim and Akim: >> An obvious, though not very elegant, solution would be to bootstrap >> like this instead: >> -- >> #!/bin/sh >> >> noreadme= >> test -f README || noreadme=yes >> test x$noreadme = x || touch README >> set -x >> aclocal >> autoheader >> automake -i --add-miss

Re: ac_config_libobj_dir broken

2002-09-09 Thread Akim Demaille
| > From: Akim Demaille <[EMAIL PROTECTED]> | > Date: 06 Sep 2002 13:50:20 +0200 | > | > > "Andreas" == Andreas Schwab <[EMAIL PROTECTED]> writes: | > | > Andreas> The default value of ac_config_libobj_dir is wrong, it should | > Andreas> be $srcdir. Similarily, AC_CONFIG_LIBOBJ_DIR should

Re: GNU packs with generated README

2002-09-09 Thread Akim Demaille
| An obvious, though not very elegant, solution would be to bootstrap like | this instead: | | -- | #!/bin/sh | | noreadme= | test -f README || noreadme=yes | test x$noreadme = x || touch README | set -x | aclocal | autoheader | automake -i --add-missing --copy | set +x | test x$noreadme = x ||