[Top][All Lists]

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

Re: [bug-gettext] autopoint and m4_ifndef

From: Sami Kerola
Subject: Re: [bug-gettext] autopoint and m4_ifndef
Date: Mon, 19 Aug 2013 10:08:03 +0100

On 24 July 2013 02:58, Daiki Ueno <address@hidden> wrote:
> Pavel Raiskup <address@hidden> writes:
>> Is there a reason why autopoint/gettextize is run before aclocal?
> One possible reason is that autopoint copies M4 files from a tarball
> (e.g. /usr/share/gettext/archive.dir.tar.*), rather than the standard
> aclocal directory.  They need to be processed by aclocal later.
>> (Other, quite long-term solution would be to hack aclocal to be able to
>> give us its *hardly built* list of include files, or used macros, e.g. by
>> some special option - ehm, but it may even more complicate the aclocal
>> code)
> Yeah, but I doubt that autopoint needs to trace macros defined outside
> of  Currently it traces only the following macros, which
> are usually invoked from

Would it be easiest for everyone to inform use of m4_fatal() may lead
to premature failures, and one should use AC_MSG_ERROR when possible.
For example util-linux would need following change.

diff --git a/ b/
index 2ad890b..917e1fa 100644
--- a/
+++ b/
@@ -118,11 +118,11 @@ dnl libtool-2

-  [m4_fatal([Could not locate the pkg-config autoconf
+  [AC_MSG_ERROR([Could not locate the pkg-config autoconf
     macros. These are usually located in /usr/share/aclocal/pkg.m4.
     If your macros are in a different location, try setting the
     environment variable AL_OPTS="-I/other/macro/dir" before running
-    ./ or autoreconf again.])])
+    ./ or autoreconf again.], [1])])


And maybe there should be a AC_IFM4DEFINED([what], [true], [false])
for checks like that.

Sami Kerola

reply via email to

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