Bug reports for the GNU m4 macro processor

Eric Blake | 8 Apr 2005 16:02

move to build-aux broke CVS m4


gnulib-tool --import, when parsing modules/gettext, adds
build-aux/config.rpath to the file list.  But for projects that don't yet
have a build-aux directory, such as a fresh checkout of CVS m4, this breaks:

cp: cannot create regular file `./build-aux/config.rpath': No such file or
directory

We need some way to make gnulib-tool respect the spelling of the target
project's AC_CONFIG_AUX_DIR.

--
Life is short - so eat dessert first!

Eric Blake             ebb9 <at> byu.net

headers

Oskar Liljeblad | 8 Apr 2005 20:26

Re: move to build-aux broke CVS m4

On Friday, April 08, 2005 at 08:48, Eric Blake wrote:
[..]
> gnulib-tool --import, when parsing modules/gettext, adds
> build-aux/config.rpath to the file list.  But for projects that don't yet
> have a build-aux directory, such as a fresh checkout of CVS m4, this breaks:
> 
> cp: cannot create regular file `./build-aux/config.rpath': No such file or
> directory
> 
> We need some way to make gnulib-tool respect the spelling of the target
> project's AC_CONFIG_AUX_DIR.

I submitted a patch to do this some week ago, but it won't be added
until my copyright assignment has been checked. I signed and sent
back the papers last week, so I guess they should be arriving
next week...

Regards,

Oskar Liljeblad (oskar <at> osk.mine.nu)

headers

Gary V. Vaughan | 8 Apr 2005 20:17

Re: move to build-aux broke CVS m4

Hi Eric,

Eric Blake wrote:
> gnulib-tool --import, when parsing modules/gettext, adds
> build-aux/config.rpath to the file list.  But for projects that don't yet
> have a build-aux directory, such as a fresh checkout of CVS m4, this breaks:
> 
> cp: cannot create regular file `./build-aux/config.rpath': No such file or
> directory
> 
> We need some way to make gnulib-tool respect the spelling of the target
> project's AC_CONFIG_AUX_DIR.

Here is an excerpt of CVS HEAD libtoolize that does exactly that (func
definitions should be obvious by their name, and $SED is substituted by
libtool's configure according to the findings of AC_PROG_SED):

    configure_ac=configure.in

    test -f configure.ac && configure_ac=configure.ac
    test -f "$configure_ac" \
        || func_fatal_help "\`$configure_ac' does not exist"

    # ---------------------------------------------------- #
    # Probe macro usage in configure.ac and/or aclocal.m4. #
    # ---------------------------------------------------- #

    my_sed_traces='s,#.*$,,; s,^dnl .*$,,; s, dnl .*$,,;
        /AC_CONFIG_AUX_DIR[[^_]]/  {
            s,^.*AC_CONFIG_AUX_DIR([[[  ]*\([^])]]*\).*$,auxdir=\1,; p;

(Continue reading)