[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: adding gnulib's sys_wait module to groff made Automake angry

From: Bruno Haible
Subject: Re: adding gnulib's sys_wait module to groff made Automake angry
Date: Mon, 17 Apr 2023 13:03:23 +0200

Hi Branden,

> The Automake anger looks like this.
> autoreconf: Entering directory `.'
> autoreconf: not using Gettext
> autoreconf: running: aclocal -I gnulib_m4 --force -I m4 -I gnulib_m4
> autoreconf: tracing
> autoreconf: not using Libtool
> autoreconf: running: /usr/bin/autoconf --include=gnulib_m4 --force
> autoreconf: running: /usr/bin/autoheader --include=gnulib_m4 --force
> autoreconf: running: automake --add-missing --copy --force-missing
> lib/ error: MOSTLYCLEANDIRS must be set with '=' before using 
> '+='
>   'lib/' included from here
> autoreconf: automake failed with exit status: 1
> ./bootstrap: autoreconf failed
> Now, sure enough, adding
> to right before our list of includes[1] fixes the build.

Good. This is also the way it's documented: [1] says that you need
to initialize MOSTLYCLEANDIRS in your

> ...but I'm not sure how to explain the change.

It comes up now, because 'sys_wait' is the first Gnulib module that
you are requesting that creates a generated file in a subdirectory.

> Is there some auditing mode I can run automake or
> autoreconf in that will detect this sort of problem before a gnulib
> module sampled at random provokes it?

You could check whether all variables listed in [1]
are initialized in your top-level



reply via email to

[Prev in Thread] Current Thread [Next in Thread]