Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 376431 - glibc-2.12.2 will not compile due to force unwind configuration error
Summary: glibc-2.12.2 will not compile due to force unwind configuration error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: Normal major (vote)
Assignee: The Gentoo Linux Hardened Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 06:40 UTC by darin hensley
Modified: 2011-07-26 15:16 UTC (History)
1 user (show)

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


Attachments
emerge -v glibc, make.conf, emerge --info (file1,20.87 KB, text/plain)
2011-07-26 06:41 UTC, darin hensley
Details

Note You need to log in before you can comment on or make changes to this bug.
Description darin hensley 2011-07-26 06:40:53 UTC
Using Gentoo Hardened multi lib, glibc-2.12.2 will not compile due to force unwind configuration error. System is about 3 months old built from stage3-amd64-hardened-20110526.tar.bz2.



Reproducible: Always

Steps to Reproduce:
1.emerge glibc
2.
3.
Actual Results:  
fails out

Expected Results:  
successful compile

Linux localhost 2.6.37-hardened-r7 #16 SMP Tue Jul 26 01:24:34 CDT 2011 x86_64 Intel(R) Core(TM) i3 CPU M 350 @ 2.27GHz GenuineIntel GNU/Linux
localhost / # 

localhost one # !gcc
gcc-config -l
 [1] x86_64-pc-linux-gnu-4.4.5 *
 [2] x86_64-pc-linux-gnu-4.4.5-hardenednopie
 [3] x86_64-pc-linux-gnu-4.4.5-hardenednopiessp
 [4] x86_64-pc-linux-gnu-4.4.5-hardenednossp
 [5] x86_64-pc-linux-gnu-4.4.5-vanilla
localhost one # 


Happens with [9]   hardened/linux/amd64/selinux or [17]  selinux/v2refpolicy/amd64/hardened
Comment 1 darin hensley 2011-07-26 06:41:57 UTC
Created attachment 280983 [details]
emerge -v glibc, make.conf, emerge --info
Comment 2 darin hensley 2011-07-26 06:46:04 UTC
Also wanted to state that I tried this with -march=native, but same problem.
Comment 3 Anthony Basile gentoo-dev 2011-07-26 09:14:38 UTC
It looks to me like you switched back and forth between multilib and nomultilib, breaking glibc in the process.

Can you give me a history of what profiles you switched between since building this box?

Also, I don't think its a selinux issue.  In fact, if it is the multi/nomulti lib issue, then its not even really a bug.  It just something you shouldn't do.
Comment 4 darin hensley 2011-07-26 15:16:39 UTC
This is a bug in the Selinux profile v2ref policy. Switched to selinux policy and re-emerged gcc and then glibc successfully.