After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 691545 - Build with automake-1.13 broken
Build with automake-1.13 broken
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-11 13:06 UTC by Marko Lindqvist
Modified: 2013-01-15 09:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix (407 bytes, patch)
2013-01-11 13:06 UTC, Marko Lindqvist
none Details | Review

Description Marko Lindqvist 2013-01-11 13:06:29 UTC
Created attachment 233225 [details] [review]
Fix

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

Attached patch simply removes AM_PROG_CC_STDC as earlier line already has
AC_PROG_CC that does just the thing AM_PROG_CC_STDC did.

----

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
Comment 1 Christian Persch 2013-01-11 13:17:32 UTC
Please commit to vte-0-34 branch.

> 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

Maybe the automake devs shouldn't remove that stuff, then. There's no reason I can see to remove it instead of just making it a nop.
Comment 2 Marko Lindqvist 2013-01-12 14:39:24 UTC
> There's no reason I can see to remove it instead of just making it a nop.

Then your configure script depending on old functionality of the macro would misfunction silently, or more likely give cryptic error messages at later stage. With an error message from aclocal you at least know that you have to implement things with a new way.
Comment 3 Christian Persch 2013-01-14 17:21:44 UTC
This is already fixed on 0-34; the patch appears to be against the unmaintained version 0-28 branch.
Comment 4 Marko Lindqvist 2013-01-15 09:34:28 UTC
Oh yes, sorry. Somehow I failed to check latest version properly. Patch is against 0.28 as that's what I need - OpenEmbedded still uses 0.28.