Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 478812 - =media-libs/alsa-lib-1.0.27.1 fails to build on Hardened Gentoo
Summary: =media-libs/alsa-lib-1.0.27.1 fails to build on Hardened Gentoo
Status: RESOLVED DUPLICATE of bug 478802
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-30 13:22 UTC by Coacher
Modified: 2013-07-30 14:58 UTC (History)
1 user (show)

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

Attachments
emerge --info alsa-lib (info,5.12 KB, text/plain)
2013-07-30 13:22 UTC, Coacher 		Details
build.log (build.log,82.16 KB, text/plain)
2013-07-30 13:23 UTC, Coacher 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Coacher 2013-07-30 13:22:33 UTC 
Hello.

Latest stable alsa-lib fails to build on my Hardened Gentoo amd64. On my regular Gentoo amd64 there are no problems with this package though.

Reproducible: Always
Comment 1 Coacher 2013-07-30 13:22:52 UTC 
Created attachment 354616 [details]
emerge --info alsa-lib
Comment 2 Coacher 2013-07-30 13:23:16 UTC 
Created attachment 354618 [details]
build.log
Comment 3 Agostino Sarubbo gentoo-dev 2013-07-30 13:52:48 UTC 
works for me on hardened..
Comment 4 Coacher 2013-07-30 14:00:37 UTC 
(In reply to Agostino Sarubbo from comment #3)

Hmm. As far as I unserstood there are some python-related problems building mixer module. Do you have all those warnings during build?
Comment 5 Coacher 2013-07-30 14:15:59 UTC 
Resolved it. Somehow main python version was switched from 2.7 to 3.2. After switching it back to 2.7 alsa-lib builds fine.


Though I am wondering what actions could cause such a change? The only manual intervention to this machine is running `emerge -pvuDN world` from time to time.
Comment 6 Coacher 2013-07-30 14:48:53 UTC 
(In reply to Coacher from comment #5)
> Though I am wondering what actions could cause such a change?

Tracked it via git back to the day of this machine was started for the first time. All this time I was running with main python version set to 3.2. Apparently it is set to 3.2 in stage3 for hardened nowadays.
Comment 7 Coacher 2013-07-30 14:58:36 UTC 

*** This bug has been marked as a duplicate of bug 478802 ***