| 1 |
No, this is wrong. On amd64, you should *not* use -fPIC in make.conf. |
| 2 |
That's been policy since 2004.0. It is required that -fPIC is used for |
| 3 |
shared things (such as shared libraries) and it is required that -fPIC |
| 4 |
is not used for non-shared things (such as binaries). Thus, it must not |
| 5 |
be set in make.conf, otherwise you break this. If something does not |
| 6 |
compile without using -fPIC in CFLAGS, then that is a bug. |
| 7 |
|
| 8 |
Hardened is different, however. |
| 9 |
|
| 10 |
Duncan wrote: |
| 11 |
> No, not all archs follow x86 (or whatever arch rules you are assuming) |
| 12 |
> rules. On some archs (amd64 comes to mind as that's what I use), -fPIC is |
| 13 |
> required. Gentoo amd64 officially discourages it in make.conf, so as to |
| 14 |
> hilite ebuilds which do NOT set it so they can be patched to do so, but |
| 15 |
> it's required on the arch, regardless, whether it's configured in the |
| 16 |
> source, in the ebuild, or in make.conf, so on some archs anyway, it's NOT |
| 17 |
> wrong to have it in make.conf, hardened or not. |
| 18 |
> |
Archives