search

eth4io / libkml

Automatically exported from code.google.com/p/libkml
Other
0 stars 0 forks source link

Autogen.sh fails with automake >=1.14 #190

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. With automake >=1.14, ./autogen.sh fails

This is due to a change in the way automake sets subdir-objects as the default: 
See https://github.com/sugarlabs/automake/blob/master/PLANS/subdir-objects.txt

======================
automake: warnings are treated as errors
third_party/Makefile.am:81: warning: source file '$(googletest)/src/gtest.cc' 
is in a subdirectory,
third_party/Makefile.am:81: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding 
output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same 
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
===============

Updating configure.ac to replace AM_INIT_AUTOMAKE(-Wall -Werror) with 
AM_INIT_AUTOMAKE(-Wall -Werror subdir-objects) resolves the autogen.sh problem, 
however it leads to a build problem. "Makefile:771: 
gtest-1.6.0/src/.deps/gtest-death-test.Plo: No such file or directory", etc... 
Examining the two versions of third_party/Makefile shows that indeed a Makefile 
change occurs. "include ./$(DEPDIR)/gtest-death-test.Plo" is replaced by 
"include $(googletest)/src/$(DEPDIR)/gtest-death-test.Plo".

So it would seem that gtest's location is no longer acceptable to automake.

Original issue reported on code.google.com by sebe...@gmail.com on 3 Aug 2013 at 9:46

GoogleCodeExporter commented 8 years ago 
Nevermind, this is using a branch of libkml which has updated to the latest 
gtest. Using HEAD, there are no problems. So this can be closed and perhaps 
serve as a reference in case someone wants to upgrade gtest to latest.

Original comment by sebe...@gmail.com on 3 Aug 2013 at 9:58