Summary: | combi of gcc 4.4.2 and binutils 2.20 on amd64: ld: trees.lo: relocation R_X86_64_PC32 against symbol `_length_code' can not be used when making a shared object; recompile with -fPIC | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | steffen stramm <krytzz> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | eric_chaligny, loki_val |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
machine 1
machine 2 build log machine2 |
Description
steffen stramm
2009-10-23 09:43:15 UTC
Created attachment 207980 [details]
machine 1
Created attachment 207982 [details]
machine 2
Could you attach the build.log from zlib? Created attachment 207994 [details]
build log machine2
funny, i emerged gcc 4.4.1 then 4.4.2 and binutils 2.20 again, now i can build zlib. however there are still warnings
I'd try a rebuild of world. Looks like some obscure bug, possibly because you've upgraded gcc from something really old? When I rebuild world I usually use this formula, when I've already updated everything to the newest possible version: emerge -eav --jobs=(cpus+sqrt(cpus)) --load-average=cpus --keep-going world Where cpus is the number of cores in your machine and sqrt(cpus) is the square root of the number of cpus in your machine. It will keep going and display a summary of failed packages at the end. yeah, very obscure :p i have a ~amd64 system for about 6 months, so nothing was old. thanks for the formula. :) even if its solved i wonder if it happens to other people because it really causes all kind of bugs (like cclive just segfaulting without any mention to TEXTREL or something). |