| 1 |
On Thu, Mar 10, 2011 at 5:12 AM, walt <w41ter@×××××.com> wrote: |
| 2 |
|
| 3 |
> On 03/09/2011 05:27 PM, Andrew Wilkinson wrote: |
| 4 |
> |
| 5 |
>> I have a VM image based on the amd64 hardened no-multilib profile. Today, |
| 6 |
>> when trying to emerge glibc-2.11.3 and gcc-4.4.5, the builds have been |
| 7 |
>> failing, and appear to be trying to build multilib versions, which of course |
| 8 |
>> it can't. Any idea why this would be happening? |
| 9 |
>> |
| 10 |
>> From glibc's build.log: |
| 11 |
>> |
| 12 |
>> * Building multilib glibc for ABIs: x86 amd64 |
| 13 |
>> |
| 14 |
>> * ABI: x86 |
| 15 |
>> * CBUILD: x86_64-pc-linux-gnu |
| 16 |
>> * CHOST: x86_64-pc-linux-gnu |
| 17 |
>> * CTARGET: x86_64-pc-linux-gnu |
| 18 |
>> * CBUILD_OPT: i686-pc-linux-gnu |
| 19 |
>> * CTARGET_OPT: i686-pc-linux-gnu |
| 20 |
>> * CC: |
| 21 |
>> * CFLAGS: -m32 -march=i686 -O2 -fno-strict-aliasing |
| 22 |
>> -fno-stack-protector |
| 23 |
>> * Manual CC: x86_64-pc-linux-gnu-gcc |
| 24 |
>> |
| 25 |
> |
| 26 |
> You might try emerge -d (debug). The Changelog is loaded with comments |
| 27 |
> about building |
| 28 |
> glibc on hardened systems, so maybe they introduced a recent bug? |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
Thanks for the tip! Unfortunately someone who knows more about what portage |
| 33 |
is doing than I do will need to look at this... in my glance over it I got |
| 34 |
the impression that it was magically conjuring the x86 ABI result from the |
| 35 |
ether, or something. |
| 36 |
|
| 37 |
I've put it up on pastebin for now. If this is something bug worthy, I'll |
| 38 |
thus report. |
| 39 |
|
| 40 |
http://pastebin.com/vS6BMhJN |
| 41 |
|
| 42 |
Thanks again! |
| 43 |
|
| 44 |
-Andy |
Archives