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 67319 - [PATCH] Fails to build with autoconf 2.52
[PATCH] Fails to build with autoconf 2.52
Status: RESOLVED FIXED
Product: bonobo
Classification: Deprecated
Component: general
1.0.x
Other other
: Normal normal
: ---
Assigned To: Michael Meeks
Michael Meeks
Depends on:
Blocks:
 
 
Reported: 2001-12-20 16:36 UTC by Enrico Scholz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch against 1.0.17 (2.94 KB, patch)
2001-12-20 16:37 UTC, Enrico Scholz 		none Details | Review

Description Enrico Scholz 2001-12-20 16:36:33 UTC 
bonobo 1.0.17 fails to build with autoconf 2.52/automake 1.5. I will attach
a patch against the sources of version 1.0.17. After applying it, it must
be executed

| autoreconf -i -f

This method REQUIRES the intltools do be installed and conflicts with old
xml-i18n-tools (the perl-interpreter macroname has been changed there).



Description of changes:
=======================

- constructs like 'CLEANFILES += ....' and 'LDFLAGS += ...' are removed;
automake rejects them because '+=' works only with GNU make.

- libefs/configure.in:
  * fixed broken quotening; autoconf 2.52 handles this more strict
  * added AM_MAINTAINER_MODE; this make life easier for people just wanting
to compile it...

- gshell/Makefile.am
  * removed duplicate 'uidir' statements; automake rejects them

- Makefile.am
  * added 'ACLOCAL_AMFLAGS=  -I macros' which allows autoreconf to work

- test/Makefile.am
  * removed trailing '\' on a comment; automake 1.5 interprets the next
non-text line as comment also. This may be a automake bug, but there are
not any drawbacks when removing the '\'...
Comment 1 Enrico Scholz 2001-12-20 16:37:32 UTC 
Created attachment 6281 [details] [review]
Patch against 1.0.17
Comment 2 Luis Villa 2002-01-25 16:47:54 UTC 
michael: is this useful/relevant anymore?
Comment 3 Michael Meeks 2002-02-02 23:22:38 UTC 
The majority of this is now fixed in CVS - can you re-open a bug if
you have further issues ?

Thanks for your report.