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 681555 - Use autoreconf instead copied gnome-autogen
Use autoreconf instead copied gnome-autogen
Status: RESOLVED FIXED
Product: yelp-tools
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-09 20:19 UTC by Javier Jardón (IRC: jjardon)
Modified: 2013-02-12 15:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use-autoreconf-instead-gnome-autogen (15.59 KB, patch)
2012-08-09 20:19 UTC, Javier Jardón (IRC: jjardon)
committed Details | Review

Description Javier Jardón (IRC: jjardon) 2012-08-09 20:19:40 UTC
Created attachment 220839 [details] [review]
Use-autoreconf-instead-gnome-autogen

Lets use the upstream tool instead copy and paste ;)
Comment 1 Sam Thursfield 2012-08-15 15:28:00 UTC
It actually causes problems having gnome-autogen.sh in the source tree

BusyBox shell (this may be a bug) will always . (source) from the current directory if the file exists there, even if a version in the PATH exists, so the bundled gnome-autogen.sh is used and it's very out of date, so for example the  build will fail if automake <= 1.9 is not installed.

When bash is in POSIX mode, . (source) will only look for gnome-autogen.sh in the PATH, not in the current directory, so in most cases the file has no way of being used.

In short, please merge this patch, I have tested myself and it works great  :)
Comment 2 Javier Jardón (IRC: jjardon) 2013-02-12 15:51:38 UTC
Comment on attachment 220839 [details] [review]
Use-autoreconf-instead-gnome-autogen

This has been commited in 	758fc9f914de88dfae80aa43d25c089dde0a8a15