The script is dead, long live autoconf!

dalibor topic dalibor.topic at
Tue Feb 6 09:36:41 UTC 2018

On 06.02.2018 09:51, Thomas Stüfe wrote:
> You are right, maybe adapting to autoconf 2.69 is the cleaner way to go
> instead of trying to make the builds run with an older autoconf.
It most likely is.

The older the autoconf is that one requires, the more problematic using 
the OS provided one becomes, as due to the murky past of autotools, OS 
vendors used to patch them quite extensively to try to work around the 
effects of incompatibilities in transitions between 2.13 and 2.50.

The autoconf civil wars took many years to settle down. See for an example 
of the accidental complexity that the whole thing triggered.

dalibor topic
<> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961

ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

<> Oracle is committed to developing
practices and products that help protect the environment

More information about the build-dev mailing list