Build error: automake-1.14: command not found

[cristid9]

The build fails on a machine with automake-1.15 installed:

cd . && automake-1.14 --gnu /bin/bash: line 4: automake-1.14: command not found Makefile:928: recipe for target 'Makefile.in' failed make: *** [Makefile.in] Error 1

You might reconsider hard-coding
am__api_version='1.14'
in configure and
/usr/share/automake-1.14/test-driver
in test-driver ?

[cjliux]

I am facing with the same error as you have.

[oren-yowza]

+1
Ubuntu 16.04 comes with automake 1.15 and my build system fails for missing symbolic link (test-driver).

[antinucleon]

Change your Makefile to

ACLOCAL = aclocal-1.15                                                                                                                                    
AUTOMAKE = automake-1.15    

and ln -s test-driver to test-driver -> /usr/share/automake-1.15/test-driver will solve that

[oren-yowza]

It's very easy for manual fix, but our automatic build system clones the git and tries to install, but fails for missing soft-link (the test-driver).
Having a soft-link to a specific-versioned-file is problematic.

[antinucleon]

antinucleon/glog@bb9f63a

On Wed, Mar 15, 2017 at 01:44 Oren ***@***.***> wrote: It's very easy for manual fix, but our automatic build system clones the git and tries to install, but fails for missing soft-link (the test-driver). Having a soft-link to a specific-versioned-file is problematic. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#165 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABM13hsN0nzk0ha_AuIuehpvbLdUB0PVks5rl6TegaJpZM4L6Bqs> .

-- Sent from mobile phone

[cristid9]

@antinucleon What if a new version of automake is released? Wouldn't a more dynamic approach be better than just hard-coding the last version?

[antinucleon]

We can use a script to update that. But for my personal use, I wont write such a script.

On Wed, Mar 15, 2017 at 10:28 Cristi D ***@***.***> wrote: @antinucleon <https://github.com/antinucleon> What if a new version of automake is release? Wouldn't a more dynamic approach be better than just hard-coding the version? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#165 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABM13h_Dmbm7feX9p39mf7Hhy3v8EjMcks5rmB_GgaJpZM4L6Bqs> .

-- Sent from mobile phone

[shinh]

Git doesn't preserve timestamps so make unnecessarily tries to rebuild auto-generated files. Maybe we should just remove generated files from the repository and ask users to run ./autogen.sh before ./configure.

[KalmanBodor]

Why is this issue closed?
The newest release at this date (0.3.5) doesn't include your changes.

I'm trying to build caffe on Ubuntu 16.04, what am I supposed to do now? Interfere somehow with cmake to patch the glog code with your commit?

You said changing the Makefile to use the newer version of aclocal, but as @oren-yowza and @cristid9 mentioned, it's not something you want to maintain.
Nonetheless, I tried that and it failed with
CMakeFiles/glog.dir/build.make:111: recipe for target 'external/glog-prefix/src/glog-stamp/glog-build' failed make[2]: *** [external/glog-prefix/src/glog-stamp/glog-build] Error 2 CMakeFiles/Makefile2:99: recipe for target 'CMakeFiles/glog.dir/all' failed make[1]: *** [CMakeFiles/glog.dir/all] Error 2

Update: I managed to install caffe by changing cmake/External/glog.cmake in the caffe source, commenting the GIT_TAG line and adding a new line:
GIT_VERSION "4f3e18bf26cdb794fc66cec348f57b5838a0c929"
(this is the commit mentioned above).