URL:
<http://gna.org/bugs/?10636>
Summary: The autoconf should check the autoconf version
Project: Battle for Wesnoth
Submitted by: None
Submitted on: Wednesday 01/02/2008 at 03:38 CET
Category: Bug
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: None of the others
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.3.13
Operating System: GNU/Linux
_______________________________________________________
Details:
Abstract:
from version 1.3.13, compiling wesnoth requires autoconf 2.61. The
compilation chain should check that at least that version is installed.
Bug report is minor as autoconf (GNU Autoconf) 2.61 seems quite old already.
Detail:
>From the version 1.3.13, I started to be unable to compile wesnoth:
The significant error message was:
> ./autogen.sh
aclocal:configure.ac:61: warning: macro `AM_GNU_GETTEXT' not found in
library
configure.ac:887: error: possibly undefined macro: BOOST_CPPFLAGS
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:888: error: possibly undefined macro: BOOST_IOSTREAMS_LDFLAGS
configure.ac:889: error: possibly undefined macro: BOOST_IOSTREAMS_LIBS
configure.ac:894: error: possibly undefined macro:
BOOST_UNIT_TEST_FRAMEWORK_LDFLAGS
configure.ac:895: error: possibly undefined macro:
BOOST_UNIT_TEST_FRAMEWORK_LIBS
configure:13807: error: possibly undefined macro: _AS_ECHO_LOG
configure:13808: error: possibly undefined macro: _AC_DO_STDERR
checking build system type
The last two errors were fatal at configuration time with the message:
> ./configure
...[snipped]
checking how to run the C++ preprocessor... g++ -E
checking boost/iostreams/device/file_descriptor.hpp usability... yes
checking boost/iostreams/device/file_descriptor.hpp presence... yes
checking for boost/iostreams/device/file_descriptor.hpp... yes
checking for the Boost iostreams library... ./configure: line 13807: syntax
error near unexpected token `re-using'
./configure: line 13807: ` _AS_ECHO_LOG(re-using the existing
conftest.$ac_objext)'
After investigation is seems the problem was with the version of my autoconf
tool. I had:
> autoconf --version
autoconf (GNU Autoconf) 2.59
After upgrading to autoconf (GNU Autoconf) 2.61, I was able to build
wesnoth.
To free the users from the hussle to investigate that compilation error, the
best would be that the configuration chain in wesnoth checks the version of
autoconf itself.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?10636>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
