[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: configure.in vs. configure.ac clash
|
From: |
Denis Barbier |
|
Subject: |
Re: configure.in vs. configure.ac clash |
|
Date: |
Mon, 4 Mar 2002 22:28:26 +0100 |
|
User-agent: |
Mutt/1.2.5i |
On Sat, Mar 02, 2002 at 03:59:32PM +0100, Alexandre Duret-Lutz wrote:
> >>> "gd" == Guido Draheim <address@hidden> writes:
>
> gd> while trying to create an rpm for the mp4h project, I jumped on the
> gd> following problem:
>
> gd> - the toplevel configure has configure.ac
> gd> - a subdir libltdl/ is copied in, which contains a configure.in
> gd> - the rpm macro %configure will expand to a line like
> gd> CFLAGS=$RPM_CFLAGS configure --prefix ....
> gd> - the toplevel configure will call the the ltdl/configure using...
> gd> configure sometarget --prefix... 'CFLAGS=$expanded_RPM_CFLAGS'
>
> gd> and BOOM. Yepp, I can fix it while *not* using %configure
> gd> with the extra CFLAGS settings.
>
> The real fix is to rerun autoconf in both directories to make
> sure the configure is generated by the same version of Autoconf
> (Your libltdl/configure obviously comes from Autoconf 2.13).
[...]
Manual section `Configuring Other Packages in Subdirectories' does say
nothing for such a requirement. Is it a feature?
If yes, why does autoconf not generate configure scripts within
subdirectories?
Denis