Unable to Compile 1.8
Moderators: Forum Moderators, Developers
9 posts
• Page 1 of 1
Unable to Compile 1.8
Using Ubuntu 10.04 32 bit, when I attempt to compile with cmake I get the following:
With scons I get the following error that seems correctable, but I can't seem to locate which package it is I need
Finally, with autotools
Thanks in advance for the help!
edit: I figure this might be relevant for the scons error:
Looks like some of those errors are errors with gcc? Maybe I ought to file a bug report with GNU
- Code: Select all
[ 84%] Building CXX object src/CMakeFiles/wesnoth-core.dir/util.cpp.o
[ 84%] Building CXX object src/CMakeFiles/wesnoth-core.dir/version.cpp.o
In file included from /usr/include/c++/4.4/map:60,
from /home/ryan/Downloads/wesnoth-1.8/src/serialization/string_utils.hpp:22,
from /home/ryan/Downloads/wesnoth-1.8/src/version.cpp:16:
/usr/include/c++/4.4/bits/stl_tree.h:297: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[2]: *** [src/CMakeFiles/wesnoth-core.dir/version.cpp.o] Error 1
make[1]: *** [src/CMakeFiles/wesnoth-core.dir/all] Error 2
make: *** [all] Error 2
With scons I get the following error that seems correctable, but I can't seem to locate which package it is I need
- Code: Select all
Checking for gzip support in Boost Iostreams... (cached) no
Base prerequisites are not met.
Client prerequisites are not met. wesnoth, cutter and exploder cannot be built.
Unit tests are disabled because their prerequisites are not met.
If any config checks fail, look in build/config.log for details
If a check fails spuriously due to caching, use --config=force to force its rerun
scons: done reading SConscript files.
scons: Building targets ...
error_action(["wesnoth"], [])
scons: *** [wesnoth] Target disabled because its prerequisites are not met
scons: building terminated because of errors.
Finally, with autotools
- Code: Select all
make[3]: Entering directory `/home/ryan/Downloads/wesnoth-1.8/po'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/ryan/Downloads/wesnoth-1.8/po'
make[2]: Leaving directory `/home/ryan/Downloads/wesnoth-1.8/po'
Making all in m4
make[2]: Entering directory `/home/ryan/Downloads/wesnoth-1.8/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/ryan/Downloads/wesnoth-1.8/m4'
Making all in src
make[2]: Entering directory `/home/ryan/Downloads/wesnoth-1.8/src'
if [ "exported" = "" ] || [ "exported" = "exported" ]; then echo '' >/tmp/westemp$$; \
else echo '#define REVISION "exported"' >/tmp/westemp$$; fi;\
if cmp -s revision.hpp /tmp/westemp$$ 2>/dev/null; then :; else cp /tmp/westemp$$ revision.hpp; fi; \
if [ -e /tmp/westemp$$ ]; then rm /tmp/westemp$$; fi
depbase=`echo version.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I/usr/include/lua5.1 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -pthread -D_REENTRANT -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -DHAVE_REVISION -I../intl -I../intl -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -DWESNOTH_PATH=\"/usr/local/share/wesnoth\" -DLOCALEDIR=\"translations\" -DHAS_RELATIVE_LOCALEDIR=1 -DFIFODIR=\"/usr/local/var/run/wesnothd\" -DWESNOTH_PREFIX=\"/usr/local\" -Werror -Wno-unused-parameter -O2 -W -Wall -ansi -DDISABLE_POOL_ALLOC -DHAVE_FRIBIDI -I/usr/include/fribidi -D_X11 -I/usr/include -MT version.o -MD -MP -MF $depbase.Tpo -c -o version.o version.cpp &&\
mv -f $depbase.Tpo $depbase.Po
In file included from /usr/include/c++/4.4/map:60,
from serialization/string_utils.hpp:22,
from version.cpp:16:
/usr/include/c++/4.4/bits/stl_tree.h:297: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[2]: *** [version.o] Error 1
make[2]: Leaving directory `/home/ryan/Downloads/wesnoth-1.8/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ryan/Downloads/wesnoth-1.8'
make: *** [all] Error 2
Thanks in advance for the help!
edit: I figure this might be relevant for the scons error:
- Code: Select all
ryan@ryan-laptop:~/Downloads/wesnoth-1.8$ apt-cache policy libboost-iostreams1.40-dev
libboost-iostreams1.40-dev:
Installed: 1.40.0-4ubuntu4
Candidate: 1.40.0-4ubuntu4
Version table:
*** 1.40.0-4ubuntu4 0
500 http://mirror.cs.umn.edu/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
Looks like some of those errors are errors with gcc? Maybe I ought to file a bug report with GNU
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
Re: Unable to Compile 1.8
I tried using gcc 4.3, and got the following:
And again,
HALP!
- Code: Select all
ryan@ryan-laptop:~/Downloads/wesnoth-1.8$ CC=gcc-4.3 CXX=g++-4.3 ./autogen.sh
...
checking for compress in -lz... yes
checking for LUA... no
checking for LUA... yes
checking for LIBDBUS... yes
checking for notifications... yes
checking for Boost headers version >= 1.35... no
configure: error: Could not find Boost headers version >= 1.35
And again,
- Code: Select all
libboost1.40-all-dev:
Installed: 1.40.0-4ubuntu4
Candidate: 1.40.0-4ubuntu4
Version table:
*** 1.40.0-4ubuntu4 0
500 http://mirror.cs.umn.edu/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
HALP!
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
Re: Unable to Compile 1.8
[quote="ryan"]
Run scons with --config=force and attach build/config.log if it still fails.
- Code: Select all
Checking for gzip support in Boost Iostreams... (cached) no
Run scons with --config=force and attach build/config.log if it still fails.
"meh." - zookeeper
-

loonycyborg - Windows Packager
- Posts: 262
- Joined: April 1st, 2008, 4:45 pm
- Location: Russia/Moscow
Re: Unable to Compile 1.8
Attached is build/config.log
- Attachments
-
config.log- (8.06 KiB) Downloaded 243 times
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
Re: Unable to Compile 1.8
The log says that test program compiled by scons causes the compiler to segfault. No idea why you're getting those segfaults though. I've compiled wesnoth with gcc 4.4.2 successfully previously. Probably you need to upgrade gcc.
"meh." - zookeeper
-

loonycyborg - Windows Packager
- Posts: 262
- Joined: April 1st, 2008, 4:45 pm
- Location: Russia/Moscow
Re: Unable to Compile 1.8
- Code: Select all
ryan@ryan-laptop:~/Downloads/wesnoth-1.8$ apt-cache policy gcc-4.4
gcc-4.4:
Installed: 4.4.3-4ubuntu5
Candidate: 4.4.3-4ubuntu5
Version table:
*** 4.4.3-4ubuntu5 0
500 http://mirror.cs.umn.edu/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
I tried forcefully reinstalling gcc, build-essential, and libboost-dev-all, still nothing.
edit: I'm running debsums -a in the off chance that a package got hit by a cosmic ray or something.
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
Re: Unable to Compile 1.8
Weird, I installed a clean 64-bit VM, ran sudo apt-get update && sudo apt-get install scons liblua5.1-dev build-essential && sudo apt-get build-dep wesnoth && sudo apt-get upgrade
downloaded the source
and scons is compiling it just fine.
I'm checking now also in a 32 bit VM... If it works there, it would appear that something or another is somehow corrupted in my host install. Oh well, seems to be a problem on my end, thanks!
edit: Also, I wonder if it matters that my host is running the 32-bit kernel with pae? The 32-bit VM is just running generic kernel.
I think I'll just install 64 bit, I think they've ironed out the issues with flash now, so no reason not to.
downloaded the source
and scons is compiling it just fine.
I'm checking now also in a 32 bit VM... If it works there, it would appear that something or another is somehow corrupted in my host install. Oh well, seems to be a problem on my end, thanks!
edit: Also, I wonder if it matters that my host is running the 32-bit kernel with pae? The 32-bit VM is just running generic kernel.
I think I'll just install 64 bit, I think they've ironed out the issues with flash now, so no reason not to.
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
Re: Unable to Compile 1.8
I know this is a week or so old, but the repo's for Lucid have the 1.8 files already....no reason to compile. 
EDIT: probably a stupid question, but did you install the DEV versions of all packages?
EDIT: probably a stupid question, but did you install the DEV versions of all packages?
"In German you'd be called a "Stehaufmaennchen" (about: stand-up-guy)...you're absent from wesnoth so long that one thinks your campaign is dead but you always come back. ;)" -Anonymissimus about SkeleRanger and ToaM
- admiralspark
- Posts: 10
- Joined: August 14th, 2009, 2:01 am
Re: Unable to Compile 1.8
I found that it was definitely a bug (I know this makes absolutely no sense and sounds impossible) with the pae kernel in Ubuntu 10.04.
I was able to successfully compile in a fresh 32 bit VM (using generic kernel), a 64 bit VM, and a 64 bit host. The only time I ran into a problem (I reinstalled twice, and verified the installation media integrity) was when I used a 32 bit host to compile (using the pae kernel).
I really should file a bug report, not sure if the kernel is to blame or gcc, (also, I realize this makes no sense, but I tested it several times from clean installs).
Anyway, I just went with a 64 bit install, the only reason I went with 32 bit in the first place was that there is no debug player for Flash in 64 bit, and I occasionally do Flex development, but I found a work around that allowed me to wrap the 32 bit debug player.
Good to know that 1.8 is in the repos though!
I was able to successfully compile in a fresh 32 bit VM (using generic kernel), a 64 bit VM, and a 64 bit host. The only time I ran into a problem (I reinstalled twice, and verified the installation media integrity) was when I used a 32 bit host to compile (using the pae kernel).
I really should file a bug report, not sure if the kernel is to blame or gcc, (also, I realize this makes no sense, but I tested it several times from clean installs).
Anyway, I just went with a 64 bit install, the only reason I went with 32 bit in the first place was that there is no debug player for Flash in 64 bit, and I occasionally do Flex development, but I found a work around that allowed me to wrap the 32 bit debug player.
Good to know that 1.8 is in the repos though!
- ryan
- Posts: 10
- Joined: April 4th, 2008, 7:34 am
9 posts
• Page 1 of 1
Return to Release Announcements, Compiling & Installation
Who is online
Users browsing this forum: Yahoo [Bot] and 2 guests