Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 312791 - games-strategy/wesnoth-1.8 fail during linking executable
Summary: games-strategy/wesnoth-1.8 fail during linking executable
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Games
URL:
Whiteboard:
Keywords:
: 314591 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-02 12:32 UTC by Piotr
Modified: 2010-04-10 23:35 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,320.31 KB, text/plain)
2010-04-02 12:33 UTC, Piotr
Details
build-with_boost_1.35.log (games-strategy:wesnoth-1.8:20100405-140246.log,136.18 KB, text/plain)
2010-04-07 00:33 UTC, Fabio Bonfante
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr 2010-04-02 12:32:26 UTC
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
Comment 1 Piotr 2010-04-02 12:33:46 UTC
Created attachment 226263 [details]
build.log

here is build.log
Comment 2 Mr. Bones. (RETIRED) gentoo-dev 2010-04-02 15:34:03 UTC
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.
Comment 3 Piotr 2010-04-03 00:18:23 UTC
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.
Comment 4 Mr. Bones. (RETIRED) gentoo-dev 2010-04-03 00:24:57 UTC
There's a problem with your system.  Otherwise, the ebuild's fine and works for the general case.
Comment 5 Piotr 2010-04-03 00:49:36 UTC
Why depending on architecture it requires different boost version? What difference here architecture makes?
Comment 6 Zeev Tarantov 2010-04-03 11:13:22 UTC
Why are you forcing amd64 to install boost 1.35 ? I have Wesnoth 1.8 working fine with boost 1.42 on ~amd64.
Comment 7 Piotr 2010-04-03 11:27:06 UTC
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?
Comment 8 Zeev Tarantov 2010-04-03 12:34:08 UTC
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.
Comment 9 Cesar Garcia 2010-04-04 01:24:28 UTC
(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.
Comment 10 Fabio Bonfante 2010-04-07 00:33:26 UTC
Created attachment 226797 [details]
build-with_boost_1.35.log
Comment 11 Fabio Bonfante 2010-04-07 00:45:57 UTC
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 ?
Comment 12 Mr. Bones. (RETIRED) gentoo-dev 2010-04-10 23:35:47 UTC
*** Bug 314591 has been marked as a duplicate of this bug. ***