Menu

#1182 Build with automake-1.13 broken

closed-fixed
None
5
2013-06-21
2013-01-12
No

Automake-1.13 removed long obsolete AM_CONFIG_HEADER completely (
http://lists.gnu.org/archive/html/automake/2012-12/msg00038.html ) and errors
out upon seeing it.

Attached patch replaces it with proper AC_CONFIG_HEADERS.


There's another curl specific problem, I have not provided a patch without knowing how you want it resolved.
Your override of AC_CONFIG_MACRO_DIR causes aclocal to fail with cryptic error messages. In practice aclocal fails to see what directory it should be using (given normally by AC_CONFIG_MACRO_DIR).


I'm mass-submitting automake-1.13 fixes. Please see what you can do so
I don't need to do the same when automake-1.14 comes out:
http://cazfi.livejournal.com/195108.html

1 Attachments

Discussion

  • Daniel Stenberg

    Daniel Stenberg - 2013-01-12

    Thanks for your report. I believe this problem is already adressed in git. I assume your bug report concerns a released version?

     
  • Daniel Stenberg

    Daniel Stenberg - 2013-01-12
    • milestone: -->
     
  • Marko Lindqvist

    Marko Lindqvist - 2013-01-12

    Yes, I've been working against 7.28.1. After fixing first dozen or so packages for automake-1.13 I found it too time consuming to checkout latest development sources of all the projects just to check if things are already fixed there.

     
  • Daniel Stenberg

    Daniel Stenberg - 2013-01-12

    I find that a rather lame excuse. This way you'll end up filing bug reports to numerous of projects that already fixed the problem. I believe we already have this fixed so I'll close this report soon unless someone says there's a lingering bug.

    (And if this was a big task for you, I'd say it suggests that automake was the wrong party here who unnecessarily removed a macro used by many projects so possibly it would've been easier to file a single bug report to them...)

     
    • Marko Lindqvist

      Marko Lindqvist - 2013-01-12

      (And if this was a big task for you, I'd say it suggests that automake
      was the wrong party here who unnecessarily removed a macro used by many
      projects so possibly it would've been easier to file a single bug report
      to them...)

      For the record, Stefano Lattarini of automake has already admitted that he made a mistake in how deprecation was handled: http://lists.gnu.org/archive/html/autoconf/2013-01/msg00007.html But that doesn't help now that mistake has already been made.

       
      • Daniel Stenberg

        Daniel Stenberg - 2013-01-12

        They could have re-instated the macro and done a bug-fix release...

         
  • Daniel Stenberg

    Daniel Stenberg - 2013-01-12
    • status: open --> pending-invalid
    • assigned_to: Daniel Stenberg
     
  • Daniel Stenberg

    Daniel Stenberg - 2013-01-14

    We believe this problem is fixed

     
  • Daniel Stenberg

    Daniel Stenberg - 2013-01-14
    • status: pending-invalid --> closed-fixed
     
Monday.com Logo