[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_REQUIRE hell
From: |
Ralf Wildenhues |
Subject: |
Re: AC_REQUIRE hell |
Date: |
Mon, 29 Dec 2008 22:55:04 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
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 configure.ac, 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
<http://thread.gmane.org/gmane.comp.sysutils.autoconf.bugs/6421/focus=6429>.
Thanks for the bug report.
Cheers,
Ralf
- AC_REQUIRE hell, Akim Demaille, 2008/12/12
- Re: AC_REQUIRE hell,
Ralf Wildenhues <=