[Top][All Lists]

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


From: Akim Demaille
Subject: Re: AC_REQUIRE hell
Date: Tue, 30 Dec 2008 11:52:01 +0100

Le 29 déc. 08 à 22:55, Ralf Wildenhues a écrit :

Hi Akim,

* Akim Demaille wrote on Fri, Dec 12, 2008 at 11:17:08AM CET:

There must be something not going too well in the AC_REQUIRES of ltld. In the attached, some macros are issued out of order, which results in, for instance, shrext_cmds being used before its definition:
I have a simple work around: instead of

AC_DEFUN([URBI_LTDL], [my macro])

I have

AC_DEFUN([URBI_LTDL], [m4_fatal([should never be used])])
m4_define([URBI_LTDL], [my macro])

The first line is to have aclocal notice that the macro is defined in an m4/ file, and the second is to avoid that URBI_LTDL define an AC_REQUIRE boundary. I don't remember the details, but it seems suspicious to me that code using shrext_cmds is emitted before the contents of my macro. Either somewhere there are m4_define that should be AC_DEFUN to define
the AC_REQUIRE barriers (an error in Libtool), or when a macro OUTER
invokes a macro INNER which requires REQUIRED then REQUIRED is output
before OUTER, which seems wrong to me (an error in Autoconf).

Without having tested it, this looks like another instance of
< >.

yes, I agree it looks very much the same.


reply via email to

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