On 3 Jun, Bill Currie wrote:
>> I've just updated autoconf from 2.13 to 2.5x recently. Now configure.in
>> uses different keywords, so the autoconf versions are not compatible.
>
> Not really true. Yes, 2.5x has new macros that aren't in 2.13, and 2.5x is
> more strict about various things, but quakeforge has successfully made it so
> both 2.13 and 2.5x (plus the various incarnations of automake and libtool)
> work with the one set of auto* files.
>
> Yes, it was hard work, but having access to both a redhat 6.2 and debian sid
> system at the same time helped a lot :)
The macros which checked for the existence of uint8_t, int8_t, ...
didn't worked with autoconf 2.53, I had to rewrite them to 2.53 syntax.
At the moment nobody with write access to the LAME CVS repository really
complained (I've just seen 'comments' from Robert and Gabriel).
autoconf 2.53 has bad docs (incomplete and contains errors), I had to
invest a lot of time last sunday for the rewrite of the *int*_t tests
because of this. That was no fun! I'm fine if someone sends me patches
which offers the possibility to generate the files with autoconf 2.13
too, but I definitivly will not produce them myself (FreeBSD offers the
possibility to have 2.13 and 2.53 installed at the same time, so I can
at least test patches in both cases with minor hasle).
Bye,
Alexander.
--
0 and 1. Now what could be so hard about that?
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
