#1123 Build problem with cvs-trunk and automake 1.12


cvs update: Updating term/lua
cvs update: Updating tutorial
cvs update: Updating win
==> CVS checkout done or server timeout
configure.in:28: error: automatic de-ANSI-fication support has been removed
/usr/share/aclocal-1.12/protos.m4:12: AM_C_PROTOTYPES is expanded from...
configure.in:28: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: /usr/bin/autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
==> ERROR: A failure occurred in build().


  • Ethan Merritt

    Ethan Merritt - 2012-05-04

    It is IMHO a bit rude of the automake developers to break this with only a perfunctory effort at notifying package maintainers or the developers of non-GNU projects. Apparently they decided last June that it was OK to remove support for non-ANSI toolchains, and figured anyone using the old macros and ansi2knr conversion support would find out the hard way.

    On the other hand, gnuplot's own documentation has warned since about 1999 that support for non-ANSI C would go away "very soon". We just never acted on that warning :-)

    Anyhow, let's do this in two stages. I've just commited to 4.7 CVS a patch that removes invocation of the deprecated macro and automake options, and instead unconditionally #defines PROTOTYPES so that the existing gnuplot source code is happy. If this doesn't uncover further problems, in a second stage we can remove checks for PROTOTYPES in the code itself.

    We'll probably have to do this for 4.6 CVS also, since I imagine that the next round of distro releases will include automake 1.12.

    I tested the revised code using automake 1.11. Please confirm that the new automake works also.

  • Stefan Husmann

    Stefan Husmann - 2012-05-05

    I confirm that your solution works. Thank you for the quick fix.

  • Ethan Merritt

    Ethan Merritt - 2012-05-05
    • status: open --> closed-fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks