[Top][All Lists]

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

Re: automake/autoreconf: Incomprehensible error messages bugs

From: Noah Misch
Subject: Re: automake/autoreconf: Incomprehensible error messages bugs
Date: Tue, 25 Jan 2005 01:37:10 -0800
User-agent: Mutt/1.5.6i

On Sun, Jan 23, 2005 at 09:28:36AM -0800, Bruce Korb wrote:
> > $ autoreconf
> > autoreconf: AM_GNU_GETTEXT is used, but not 

> 1.  The automake example of AM_GNU_GETTEXT does not show
>      AM_GNU_GETTEXT_VERSION being used in conjunction with it.
>     In fact, it isn't even documented at all.

See the gettext documentation.  `autopoint' uses AM_GNU_GETTEXT_VERSION (and
fails without it), so `autoreconf' does not run `autopoint' if `'
does not call `AM_GNU_GETTEXT_VERSION'.  This is not actually a fatal error;
the message probably should begin ``autoreconf: warning: ...''.

> 2.  Surely the message, "cannot empty /tmp/ar0.4849: Is a directory"
>      can be made more meaningful.  What _does_ it mean?
>      (Besides being the error message "rm" will give you.  :)

The message is not meaningful because this Never Happens :)

autoreconf tried to delete the contents of its temporary directory, and then the
directory itself.  The former failed silently, so the latter failed noisely.  I
hit this once before with a broken Perl (Slackware 3.3, 5.004_03 IIRC) where
Perl's globbing mysteriously returned an empty list every time.  You can try a
simple `perl -e 'print <*>' in a nonempty directory; if it prints nothing, that
is your problem, too.  It certainly may be something entirely different, though.

What type of system is this?  What version of Perl?

reply via email to

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