This is all, of course, with sources from git.
If configure contains the line continuation ('\') in AC_CONFIG_FILES,
then we end up with this lovely construct in configure:
"config/Makefile") CONFIG_FILES="$CONFIG_FILES config/Makefile" ;;
"\") CONFIG_FILES="$CONFIG_FILES \" ;;
"doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;;
(I tested with configure.ac containing both styles of line-endings and
both with the same result).
If we attempt to make doc, we end up with
make[2]: Entering directory `/gnumake/make/doc'
Updating ./version.texi
make[2]: *** No rule to make target `fdl.texi', needed by `make.info'. Stop.
make[2]: Leaving directory `/gnumake/make/doc'
Which seems to be very similar to this old bug
report:http://osdir.com/ml/gnu.make.windows/2005-03/msg00077.html
Cheers,
Ray.
On Tue, Apr 16, 2013 at 3:01 PM, Eli Zaretskii <e...@gnu.org> wrote:
> Date: Tue, 16 Apr 2013 13:41:53 +0100
> > From: Ray Donnelly <mingw.andr...@gmail.com>
> >
> > This is just for reference for anyone who wants to build gnumake on
> > Windows. I don't want it to be applied as the real bugs are in Autotools.
>
> What are the bugs, and how do they manifest themselves?
>
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
