Hi Ralf,
On Sun, Mar 16, 2008 at 5:26 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > > Thanks for the report, and sorry for the long delay. Here's a cheap
> > > patch. Would this be sufficient? It requires you to use -v aka.
> > > --verbose in order to see the message.
> [...]
> > Anyway, the short answer: No. I'd still be getting some sort of
> > "command 'autopoint' not found" message without any clue about
> > what issue might be triggering it. Unless I knew a priori to autoreconf
> > with the --verbose option. I think the messages should lead me to the
> > answer without having to request verbose output.
>
> You're fully right in expecting better. What about this? OK to apply?
It is excellent, modulo a typo. Thank you! It will be excellent!
> index 66da78e..65ef014 100644
> --- a/bin/autoreconf.in
> +++ b/bin/autoreconf.in
> @@ -364,7 +364,7 @@ sub autoreconf_current_directory ()
> }
> else
> {
> - xsystem "$autopoint";
> + xsystem_hint ("autopoint is needed because this package uses
> Gettext", "$autopoint");
> }
>
>
> @@ -528,7 +528,7 @@ sub autoreconf_current_directory ()
> {
> $libtoolize .= " --ltdl";
> }
> - xsystem ($libtoolize);
> + xsystem ("libtoolize is needed because this package uses Libtool",
> $libtoolize);
"xsystem_hint", yes?
Cheers - Bruce
