Re: lib/malloca.c: error when compiling "groff"

[Bruno Haible]

Bjarni Ingi Gislason wrote:
>   I had bootstrapped at 19.55 UTC so I missed the latest commit.
> 
>   I bootstrapped at 22.39 UTC with these changes:
> 
> Updating file gnulib_m4/assert_h.m4 (backup in gnulib_m4/assert_h.m4~)
> Updating file lib/verify.h (backup in lib/verify.h~)
> 
>   I made distclean, configured, and compiled with the same error.
> 
>   I have the same last commit as you (plus some (not new) local changes
> in the groff sources).
> 
>   My malloca.c in groff/lib is
> 
> -rw------- 1 bg bg 3701 sep 14 19:54 malloca.c

When I bootstrap groff master, there is no malloca.c in the tree.

I
  - took groff git master
    $ git clone https://git.savannah.gnu.org/git/groff.git
    $ cd groff
  - added pkg.m4 to m4/ to avoid a broken 'configure' later,
    cp /usr/share/aclocal/pkg.m4 m4/
  - added an initialization of MOSTLYCLEANDIRS in Makefile.am,
  - ran
    ./bootstrap --no-git --gnulib-srcdir=$GNULIB_SRCDIR --skip-po
    where $GNULIB_SRCDIR references gnulib git master.

There is no malloca.c there.

To me, it looks like you are accumulating gnulib modules over time,
and rarely/never really do a fresh bootstrap with just the modules
listed in bootstrap.conf.

As I said earlier in
  <https://lists.gnu.org/archive/html/bug-gnulib/2022-01/msg00155.html>:
Since in groff you have a bootstrap.conf, you are not supposed to use
'gnulib-tool --add-import'. You are supposed to add new modules in
bootstrap.conf, and then run './bootstrap' with arguments.

If my guess is wrong, the problem is that you are letting me guess.
When you report an issue, you should report the steps that allow us
to reproduce it. Don't let me guess!

Bruno