[Freeciv-Dev] Re: autoconf2.5x patch
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
On Thu, Apr 18, 2002 at 05:18:16PM +0200, Per I Mathisen wrote:
> I've managed to decode, reindent and upgrade the beastial custom autoconf
> X library detection hack used in freeciv. The result is an autoconf2.5x
> version of configure.in which (barring the usual bugs) should work as fine
> for Xaw as the old one.
>
> The simple solution outlined ealier, using both configure.in and
> configure.ac simultaneously, turned out to produce an avalanche of
> warnings. So I hacked ./autogen.sh quite a bit and the result is an even
> cleaner ./autogen.sh output than was before, in addition to it selecting
> and using the right configure.in|ac file :-)
>
> I hate reading m4 macros. My brain is near the bursting point... Please
> test and give me feedback on this.
- from my understanding the old autoconf won't touch configure.ac and
the new one won't touch configure.in. So I see no reason why
configure.in should be renamed to configure.old.
- running it here produce:
$ ./autogen.sh
+ checking for autoconf >= 2.52 ... + checking for autoconf >= 2.13 ... found
2.13, ok.
+ checking for automake >= 1.4 ... found 1.4, ok.
+ checking for xgettext >= 0.10.38 ... found 0.10.39, ok.
+ checking for msgfmt >= 0.10.38 ... found 0.10.39, ok.
The first line is ugly.
- It produce warnings:
+ running autoheader ...
configure.in:360: warning: AC_TRY_RUN called without default to allow cross
compiling
+ running autoconf ...
configure.in:360: warning: AC_TRY_RUN called without default to allow cross
compiling
+ running automake ...
This is probably because of the changes in m4/x.m4. What about two
files (m4/x-ac213.m4 and m4/x-ac25.m4) or two directories (m4-ac213
and m4-ac25) (but these two dirs seems like overkill)?
Raimar
--
email: rf13@xxxxxxxxxxxxxxxxx
Tank: So what do you need? Besides a miracle.
Neo: Guns. Lots of guns.
-- From The Matrix
|
|