AC_CACHE

2005-02-07 Thread Russell Shaw
Hi, I'm updating a very old configure.in to a new configure.ac. I don't get what this does: # Check for the tigetstr/tigetnum functions. AC_MSG_CHECKING([for tigetstr/tigetstr]) AC_CACHE_VAL([gotch_cv_have_curses_tigetstr], [dnl AC_TRY_LINK([#

Re: ${prefix} expansion in configure.ac ?

2005-02-07 Thread Stepan Kasal
Hi, On Fri, Feb 04, 2005 at 03:58:51PM +0200, Philippe Trottier wrote: > CPPFLAGS=-I${prefix}/include > LDFLAGS=-L${exec_prefix}/lib > > Is there better way to expand ${prefix} other than using sed ? yes, use the shell builtin `eval'. The following macro can serve as an example: http://www.gnu.

Re: ${prefix} expansion in configure.ac ?

2005-02-07 Thread Philippe Trottier
Stepan Kasal wrote: Hi, On Fri, Feb 04, 2005 at 03:58:51PM +0200, Philippe Trottier wrote: CPPFLAGS=-I${prefix}/include LDFLAGS=-L${exec_prefix}/lib Is there better way to expand ${prefix} other than using sed ? here is something I have noticed, exec_prefix is set to NONE until the end of

Re: AC_CACHE

2005-02-07 Thread Russell Shaw
Russell Shaw wrote: Hi, I'm updating a very old configure.in to a new configure.ac. I don't get what this does: Don't worry, figured it out;) ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

Re: multiline output variables.

2005-02-07 Thread Dan Manthey
Hi, again. This took a while because I was working on other things. I hope that this is the final patch for supporting multiline output variables. (Though I bet that I've made some dumb typo.) The attached patch is 'cvs diff'ed from anoncvs as of this afternoon. On Fri, 28 Jan 2005, Stepan Kas

RFC: Changing the default docdir

2005-02-07 Thread Nicholas Wourms
Hi, I think making the default "docdir" $(datadir)/doc/$(PACKAGE) is a bad idea. The primary reason is that clobbering can occur if the user installs multiple versions of the same package (which isn't unusal in cases where compatibility issues arise between versions). This problem was delt with

Re: multiline output variables.

2005-02-07 Thread Albert Chin
On Mon, Feb 07, 2005 at 03:55:49PM -0500, Dan Manthey wrote: > I instead just ask `test ${#ac_delim} -gt 1000', which gives six > iterations with the current set up. ${#} isn't portable. I think this is: _len=`expr "${ac_delim}" : ".*"` -- albert chin ([EMAIL PROTECTED]) __

Re: RFC: Changing the default docdir

2005-02-07 Thread Bob Proulx
Nicholas Wourms wrote: > I think making the default "docdir" $(datadir)/doc/$(PACKAGE) is > a bad idea. The primary reason is that clobbering can occur if > the user installs multiple versions of the same package (which > isn't unusal in cases where compatibility issues arise between > versions).

Re: empty config.h(.in)

2005-02-07 Thread Paul Eggert
Andreas Bauer <[EMAIL PROTECTED]> writes: > AC_CONFIG_HEADERS([config.h]) > > On some machines it does create config.h(.in) as expected, i.e. with > all relevant definitions, on others the files are created but remain > rather empty! This suggests that Autoconf is not installed correctly on the

Re: multiline output variables.

2005-02-07 Thread Stepan Kasal
Hi, > > I instead just ask `test ${#ac_delim} -gt 1000', which gives six > > iterations with the current set up. > > ${#} isn't portable. I think this is: > _len=`expr "${ac_delim}" : ".*"` but this is ugly. Something like: for f in 0 1 2 3 4 5 6; do test $f = 6 && AC_MSG_ERROR(...)