| 1 |
On 03/09/2011 05:27 PM, Andrew Wilkinson wrote: |
| 2 |
> I have a VM image based on the amd64 hardened no-multilib profile. Today, when trying to emerge glibc-2.11.3 and gcc-4.4.5, the builds have been failing, and appear to be trying to build multilib versions, which of course it can't. Any idea why this would be happening? |
| 3 |
> |
| 4 |
> From glibc's build.log: |
| 5 |
> |
| 6 |
> * Building multilib glibc for ABIs: x86 amd64 |
| 7 |
> |
| 8 |
> * ABI: x86 |
| 9 |
> * CBUILD: x86_64-pc-linux-gnu |
| 10 |
> * CHOST: x86_64-pc-linux-gnu |
| 11 |
> * CTARGET: x86_64-pc-linux-gnu |
| 12 |
> * CBUILD_OPT: i686-pc-linux-gnu |
| 13 |
> * CTARGET_OPT: i686-pc-linux-gnu |
| 14 |
> * CC: |
| 15 |
> * CFLAGS: -m32 -march=i686 -O2 -fno-strict-aliasing -fno-stack-protector |
| 16 |
> * Manual CC: x86_64-pc-linux-gnu-gcc |
| 17 |
|
| 18 |
You might try emerge -d (debug). The Changelog is loaded with comments about building |
| 19 |
glibc on hardened systems, so maybe they introduced a recent bug? |
Archives