[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
|
From: |
Ralf Wildenhues |
|
Subject: |
Re: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET |
|
Date: |
Fri, 3 Jul 2009 14:33:42 +0200 |
|
User-agent: |
Mutt/1.5.20 (2009-06-15) |
Hello Rhys,
* Rhys Ulerich wrote on Thu, Jul 02, 2009 at 05:22:27PM CEST:
> I've got a macro that needs $target_cpu which is available from
> AC_CANONICAL_TARGET. Within my macro I use
> AC_REQUIRE([AC_CANONICAL_TARGET]) which triggers the following
> warning:
>
> configure.ac:47: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
> ../../lib/autoconf/general.m4:1723: AC_CANONICAL_TARGET is expanded from...
> m4/acx_mkl.m4:64: ACX_MKL is expanded from...
> configure.ac:47: the top level
>
> The easy way to eliminate the warning is to include
> AC_CANONICAL_TARGET early on in my configure.ac.
Yes, and in this case, that seems to be the right way to me.
> However, I'd like to
> have the macro strictly enforce the requirement of AC_CANONICAL_TARGET
> because I anticipate putting it up on the Autoconf macro archive once
> it gets a bit more mature.
> Are there any recommended ways to rectify the warning under that use case?
Why do you think it would be a problem for users of your macro to follow
the above advice? The current Autoconf code doesn't mangle program
names in the right way otherwise.
Cheers,
Ralf