Jim Meyering ada994274c build: handle @ALLOCA@-vs-non-recursive make problems ...

Here is a good reason to avoid alloca with non-recursive make.  These:

    $ grep @ALLOCA lib/gnulib.mk
    lib_libcoreutils_a_LIBADD += lib/@ALLOCA@
    lib_libcoreutils_a_DEPENDENCIES += lib/@ALLOCA@

would lead to this, when @ALLOCA@ expands to the empty string,
which is essentially "always", now:

    $ grep ' lib/$' Makefile
    lib_libcoreutils_a_LIBADD = $(gl_LIBOBJS) lib/
    lib_libcoreutils_a_DEPENDENCIES = $(gl_LIBOBJS) lib/

Tell the prefix-adding script not to add a prefix when the word it's
prefixing is "@ALLOCA@".  That is fine for most cases, but what about
when the expansion of @ALLOCA@ is nonempty?

* build-aux/prefix-gnulib-mk (prefix_word): Exclude @ALLOCA@.
* gl/m4/non-recursive-gnulib-prefix-hack.m4: Prefix non-empty
$ALLOCA with "lib/".  FIXME: I'm not sure this is required,
now that we...
Use AC_CONFIG_LIBOBJ_DIR([lib]).
Without using AC_CONFIG_LIBOBJ_DIR([lib]), automake (not autoconf)
would complain of failure to find aclocal.c, due to the use of
AC_LIBSOURCES(alloca.c).

2012-09-11 11:23:16 +02:00

..

build-aux

build: handle @ALLOCA@-vs-non-recursive make problems

2012-09-11 11:23:16 +02:00

lib

maint: add more control flags to mbsalign

2012-09-11 03:23:42 +01:00

m4

build: handle @ALLOCA@-vs-non-recursive make problems

2012-09-11 11:23:16 +02:00

modules

build: new module to convert lib/ to non-recursive make

2012-09-11 11:23:00 +02:00

tests

maint: add more control flags to mbsalign

2012-09-11 03:23:42 +01:00