I have synced today and I found new version of wesnoth. I wanted to update but it fails during linking the executable. Reproducible: Always Steps to Reproduce: 1. emerge -uD world or 1. emerge -1 wesnoth Actual Results: fails during linking the executable: Linking CXX executable ../wesnoth Expected Results: build correctly
Created attachment 226263 [details] build.log here is build.log
your boost is too new. I changed the ebuild to force it to use the older one. resync and try in again in a while.
On amd64 it works fine after it installed boost 1.35.0-r5 but on x86 it haven't installed old boost so the build again failed and problem remained.
There's a problem with your system. Otherwise, the ebuild's fine and works for the general case.
Why depending on architecture it requires different boost version? What difference here architecture makes?
Why are you forcing amd64 to install boost 1.35 ? I have Wesnoth 1.8 working fine with boost 1.42 on ~amd64.
I'm not forcing anything. After sync wesnoth wanted it. But previously it didn't want to link with boost-1.42 and on ~x86 it still don't want to and exit with error. What can be wrong with my systems?
Sorry Peter, I was addressing Mr. Bones. I don't have a Gentoo x86 handy to test. Can someone please verify whether the problem experienced by Peter is an x86 problem or limited to only Peter's machine? @Peter: I don't know, I would try to emerge -e system and see what happens, but that may take a while, might be completely unnecessary and likely won't fix the problem.
(In reply to comment #6) > Why are you forcing amd64 to install boost 1.35 ? I have Wesnoth 1.8 working > fine with boost 1.42 on ~amd64. > Same here (~amd64), i compiled wesnoth-1.8 with boost-1.42.0 two days ago without problems. I dont see the reason for force the 1.35 versión. P.D.: maybe Peter's problem is related to his cmake version, the error output from bug #305945 is the same as his log.
Created attachment 226797 [details] build-with_boost_1.35.log
I'm on amd64 cmake-2.6.4-r3 (stable) and installed both boost-1.35 and 1.42. The selected boost slot, as 'eselect boost list' say (didn't selected myself, probably portage does it automatically) is 1.42. Anyway cmake find and use boost-1.35 (this can be related to the other bug) but this doesn't change that the linker fail, and looking at my log file I can't say if it's related to boost. Someone else has the same error linking libwesnoth-game.a ?
*** Bug 314591 has been marked as a duplicate of this bug. ***