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 600279 - gnome-autogen.sh fails to locate automake
gnome-autogen.sh fails to locate automake
Status: RESOLVED DUPLICATE of bug 537772
Product: gnome-common
Classification: Core
Component: general
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: Gnome Common Maintainer(s)
Gnome Common Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-11-01 01:53 UTC by J.A.R.
Modified: 2013-07-19 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description J.A.R. 2009-11-01 01:53:44 UTC 
checking for automake >= 1.9...
  testing automake-1.10... not found.
  testing automake-1.9... not found.
***Error***: You must have automake >= 1.9 installed
  to build vte.  Download the appropriate package for
  from your distribution or get the source tarball at
    http://ftp.gnu.org/pub/gnu/automake/automake-1.9.tar.gz


Needless to say it's there (just not under the Debianish name "automake-$versionhere")
-rwxr-xr-x 2 root root 257125 Jun 19 16:06 /usr/bin/automake

This is on openSUSE (any version).
Comment 1 J.A.R. 2009-11-01 01:55:59 UTC 
Well, the second hardlink of the file belongs to /usr/bin/automake-1.11, which is not listed in 2.24's gnome-common (but I guess only in a later version).

But I am pretty confident gnome-automake.sh should also try automake without a trailing -version identifier nevertheless.
Comment 2 Christian Persch 2009-11-02 16:53:43 UTC 
Automake upstream installs the automake-$version binary, it's not a 'debian thing'. Given this, I don't think we should check for unversioned automake.

I think the problem is that you simply have a too old version of gnome-common; 2.28.0 added support for automake 1.11.
Comment 3 Javier Jardón (IRC: jjardon) 2013-07-19 11:12:49 UTC 

*** This bug has been marked as a duplicate of bug 537772 ***