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 591198 - Get rid of shave with AM_SILENT_RULES automake option
Get rid of shave with AM_SILENT_RULES automake option
Status: RESOLVED FIXED
Product: giggle
Classification: Other
Component: libgiggle
HEAD
Other Linux
: Normal normal
: ---
Assigned To: Mathias Hasselmann (IRC: tbf)
Depends on:
Blocks:
 
 
Reported: 2009-08-09 05:09 UTC by Javier Jardón (IRC: jjardon)
Modified: 2010-01-22 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Get rid of shave with AM_SILENT_RULES automake option (14.45 KB, patch)
2009-08-09 05:10 UTC, Javier Jardón (IRC: jjardon) 		none Details | Review
Get rid of shave with AM_SILENT_RULES (6.13 KB, patch)
2009-10-13 16:59 UTC, Javier Jardón (IRC: jjardon) 		committed Details | Review

Description Javier Jardón (IRC: jjardon) 2009-08-09 05:09:39 UTC 
A hard dependency on automake 1.11 is not necessary. Only add

m4_ifdef([AM_SILENT_RULES],[AM_SILENT_RULES])

to your configure.ac and should work and still be compatible with earlier
automake versions.


See http://live.gnome.org/GnomeGoals/NicerBuilds for more info
Comment 1 Javier Jardón (IRC: jjardon) 2009-08-09 05:10:58 UTC 
Created attachment 140250 [details] [review]
Get rid of shave with AM_SILENT_RULES automake option
Comment 2 Javier Jardón (IRC: jjardon) 2009-10-13 16:59:12 UTC 
Created attachment 145368 [details] [review]
Get rid of shave with AM_SILENT_RULES

Sorry, this is the correct patch
Comment 3 Mathias Hasselmann (IRC: tbf) 2009-10-14 08:13:40 UTC 
WONTFIX, before automake with AM_SILENT_RULES is widespread (or at least on my box).
Comment 4 Javier Jardón (IRC: jjardon) 2010-01-22 17:30:14 UTC 
Comment on attachment 145368 [details] [review]
Get rid of shave with AM_SILENT_RULES

commit a1e7659a34eec1ff0cd5e9a4938b3a89d5dfe158
Comment 5 Javier Jardón (IRC: jjardon) 2010-01-22 17:30:26 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.