Compilation failed with error: /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/parse/Lexer.cpp:8:41: fatal error: boost/spirit/home/phoenix.hpp: No such file or directory Reproducible: Always
Created attachment 392784 [details] build.log
There are no easy way to fox this. I've made a patch to change #include point to new location of phoenix.hpp. But seems like there are more changes, not only location. New errors looks like /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/parse/Lexer.cpp: In constructor ‘parse::lexer::lexer()’: /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/parse/Lexer.cpp:64:27: error: ‘boost::phoenix::construct’ has not been declared using boost::phoenix::construct; ... /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/parse/Lexer.cpp:67:9: required from here /usr/include/boost/utility/result_of.hpp:189:8: error: wrong number of template arguments (1, should be 2) struct result_of_nested_result : F::template result<FArgs> ... /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/parse/Lexer.cpp:67:9: required from here /usr/include/boost/phoenix/core/detail/preprocessed/function_eval_10.hpp:122:21: error: no type named ‘type’ in ‘struct boost::result_of<const {anonymous}::strip_quotes_(__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >&, __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >&)>’ type; Furthermore, later there are even more errors, like /tmp/portage/games-strategy/freeorion-0.4.3/work/freeorion-0.4.3/FreeOrion/GG/src/Font.cpp:1280:41: error: ambiguous overload for ‘operator>’ (operand types are ‘const unsigned int’ and ‘const GG::X’) if ((glyph_bitmap.width > BUF_WIDTH) | (glyph_bitmap.rows > BUF_HEIGHT)) { So, at least for freeorion-0.4.3 ebuild, there must be additional constraint <dev-libs/boost-1.56.0 I believe that freeorion-0.4.4 also not compatible with boost-1.56
According to this http://www.freeorion.org/index.php/Main_Page there is 0.44 available .. quote// FreeOrion 0.4.4 has been released. Windows and OSX installers are available on SourceForge. Linux users will need to build from source, or acquire from your distribution if available. Source tarballs are available from the SVN web client for which see the links on the Compile page. See this post for release notes. Geoff the Medio 12:05, 4 September 2014 (EDT)
according to this http://www.freeorion.org/forum/viewtopic.php?f=24&t=7205&start=15 Building for Gentoo Linux [64-bit], dates back to 12-december-2014 note: it only builds with boost 1.55 theres another branch that builds with 1.56 , but that segfaults upon start, so theres no linux build possible at present
according to this, someone asked for a fix, pending, state yesterday http://www.freeorion.org/forum/viewtopic.php?f=24&t=9220 Good day. I have problem with building git version together with boost-1.56. Last now in the portage tree in Gentoo.
I highly recommend to kick out freeorion out of the portage tree. 3 Months without any fixes on a package. Usually in the past packages were removed from the tree when unfixed. No maintainer and bug is unfixable, do not compile at all.
http://forums.gentoo.org/viewtopic-p-7722466.html#7722466
(In reply to Roman Gruber from comment #7) > http://forums.gentoo.org/viewtopic-p-7722466.html#7722466 (In reply to Roman Gruber from comment #7) > http://forums.gentoo.org/viewtopic-p-7722466.html#7722466 Prior to today, the last post on the FreeOrion boards regarding building in Gentoo (from December 2014) had indicated it worked fine (at which time Boost 1.55 was apparently in gentoo stable portage, if that's the right terminology). Our current code does compile fine with boost 1.56, though I'm not sure when a new debian package would get rolled out. I believe that's where you get your package from, have you tried contacting Markus, the maintainer listed on our debian page https://packages.debian.org/sid/freeorion ?
Whoops, my apologies for getting mixed up about thinking gentoo derived from debian, I guess that's no help. We do have at least one active Gentoo user, but I really don't know if he was involved in your original package or if he will get involved here. If someone tries our current code and has issues with it we'd certainly like to hear about it at the freeorion forums, but I'm not sure what else I/we could do for you in the meantime. If you have ideas on that feel free to let me know them.
Hi, I'm the maintainer of freeorion and a few hours ago is the first time I read of this problem. Let's keep honest to the facts: - It is true that freeorion does not build with the latest boost. If you need freeorion, it should be no problem however to downgrade to boost-1.55 for now. If upstream says it works fine with boost-1.56, then we'll find the reason. - the original reporter assigned this to the wrong assignee (games instead of tomka) that's why there was no reaction. Please don't assign bugs yourself unless you know what it means and have checked metadata of the package. > No maintainer and bug is unfixable, do not compile at all. All three of these statements are wrong. - We don't take our packages from Debian, Gentoo is source based, Debian is binary. - freeorion 0.4.3 is outdated, let's all focus on 0.4.4. In fact, I just removed 0.4.3. - I'll look at this as soon as possible.
It's probably this here: http://www.freeorion.org/forum/viewtopic.php?f=24&t=9206&start=0 I'll fix it tomorrow.
There were several issues that are already fixed upstream. Patching them went into a little dependency nightmire since after the 0.4.4. release several structural changes were implemented (ogre->sdl2, etc.). Long story short: I replaced 0.4.4 by an up to date snapshot 0.4.5_pre which works just fine here with any version of boost and freetype. Please open new bugs for new problems and assign them to me, or leave them for bugwranglers to assign. + 27 Mar 2015; Thomas Kahle <tomka@gentoo.org> +freeorion-0.4.5_pre.ebuild, + -freeorion-0.4.4.ebuild: + bump and remove old
Created attachment 399890 [details] 0.4.5_pre Here is what i got in newest package
(In reply to juneau_ from comment #13) > Created attachment 399890 [details] > 0.4.5_pre > > Here is what i got in newest package Something wrong with compilating that package, but i resolved the problem by adding swap file. Nevermind.
(In reply to juneau_ from comment #14) > (In reply to juneau_ from comment #13) > > Created attachment 399890 [details] > > 0.4.5_pre > > > > Here is what i got in newest package > > Something wrong with compilating that package, but i resolved the problem by > adding swap file. Nevermind. Yes, the package is very heavy. You should reduce your MAKEOPTS or increase RAM/SWAP if you run into trouble.
(In reply to Thomas Kahle from comment #10) > - the original reporter assigned this to the wrong assignee (games instead > of tomka) that's why there was no reaction. Please don't assign bugs > yourself unless you know what it means and have checked metadata of the > package. Original reporter (me) didn't know who maintain each and every package. And, IMHO, should't know. All those global facilities (e.g. games@gentoo.org, kde@gentoo.org, etc) made to dispatch bugreports to correct assignee. > - freeorion 0.4.3 is outdated, let's all focus on 0.4.4. In fact, I just > removed 0.4.3. Original bug was filed against freeorion-0.4.3 because 0.4.4 was absent in tree. No offence, but my experience show that, sometimes, maintainers need to be pushed due to various reasons. For example, because I use ~arch, while maintainer don't and don't know about a problem, which will be in future for most users.
(In reply to Denis Sokolovsky from comment #16) > (In reply to Thomas Kahle from comment #10) > > - the original reporter assigned this to the wrong assignee (games instead > > of tomka) that's why there was no reaction. Please don't assign bugs > > yourself unless you know what it means and have checked metadata of the > > package. > Original reporter (me) didn't know who maintain each and every package. And, > IMHO, should't know. All those global facilities (e.g. games@gentoo.org, > kde@gentoo.org, etc) made to dispatch bugreports to correct assignee. You can use equery m freeorion to find the maintainer, but the best thing is to not assign the bugs yourself. Our bugwranglers will do it usually within a few hours. > > > - freeorion 0.4.3 is outdated, let's all focus on 0.4.4. In fact, I just > > removed 0.4.3. > Original bug was filed against freeorion-0.4.3 because 0.4.4 was absent in > tree. No offence, but my experience show that, sometimes, maintainers need > to be pushed due to various reasons. For example, because I use ~arch, while > maintainer don't and don't know about a problem, which will be in future for > most users. That's all fine, I was only a bit annoyed by somebody storming in and demanding removal while having now clue about anything.
(In reply to Thomas Kahle from comment #17) > to find the maintainer, but the best thing is to not assign the bugs > yourself. Our bugwranglers will do it usually within a few hours. Well, I forgot to state this in previous comment: I haven't set the assignee by myself, all that I have done is component choosing. As component mandatory to specify it seems logical to choose "Games" for "games-strategy/freeorion". Assignee "games@gentoo.org" was chosen automatically from component, I believe.
(In reply to Denis Sokolovsky from comment #18) > (In reply to Thomas Kahle from comment #17) > > to find the maintainer, but the best thing is to not assign the bugs > > yourself. Our bugwranglers will do it usually within a few hours. > Well, I forgot to state this in previous comment: I haven't set the assignee > by myself, all that I have done is component choosing. As component > mandatory to specify it seems logical to choose "Games" for > "games-strategy/freeorion". Assignee "games@gentoo.org" was chosen > automatically from component, I believe. I see, sorry. That's probably a misconfiguration of our bugzilla as some games are not maintained by the games team. I'll look at it.
