bug#9459: 24.0.50; Condigure aborts, complains about missing install.sh in build-aux.

[Lars Magne Ingebrigtsen]

Paul Eggert <eggert@cs.ucla.edu> writes:

> I tried that approach, but abandoned it because it didn't work well.
> If we do something like this:
>
>          $(srcdir)/configure: $(AUTOCONF_INPUTS)
>         -       cd ${srcdir} && autoconf
>         +       cd ${srcdir} && autoconf || { \
>         +         echo 'Please run ./autogen.sh before reporting a bug.'; \
>         +         exit 1; \
>         +       }

Can't you put the message in a variable (or something)?  Either that, or
suppress printing this particular line...

> Yes, of course.  But if the failure is something that autogen.sh can
> repair (which was the case with Jan's problem), then invoking
> autogen.sh is a win.  And if it's something that autogen.sh can't
> repair, then we're no worse off than before.  So falling back on
> autogen.sh seems to be a win overall.

If the build failure is something completely irrelevant to autogen.sh
(if, for instance, we're hacking the sources), then having autogen.sh
run unexpectedly would be annoying.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/