From: Robert Moss <robmoss@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Common make.conf screwups?
Date: Sun, 21 Nov 2004 21:10:27 +0000 [thread overview]
Message-ID: <41A10443.2070108@gentoo.org> (raw)
In-Reply-To: <pan.2004.11.20.08.17.26.861682@cox.net>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
No, this is wrong. On amd64, you should *not* use -fPIC in make.conf.
That's been policy since 2004.0. It is required that -fPIC is used for
shared things (such as shared libraries) and it is required that -fPIC
is not used for non-shared things (such as binaries). Thus, it must not
be set in make.conf, otherwise you break this. If something does not
compile without using -fPIC in CFLAGS, then that is a bug.
Hardened is different, however.
Duncan wrote:
> No, not all archs follow x86 (or whatever arch rules you are assuming)
> rules. On some archs (amd64 comes to mind as that's what I use), -fPIC is
> required. Gentoo amd64 officially discourages it in make.conf, so as to
> hilite ebuilds which do NOT set it so they can be patched to do so, but
> it's required on the arch, regardless, whether it's configured in the
> source, in the ebuild, or in make.conf, so on some archs anyway, it's NOT
> wrong to have it in make.conf, hardened or not.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2004-11-21 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 19:45 [gentoo-dev] Common make.conf screwups? Ciaran McCreesh
2004-11-18 20:34 ` Robert Moss
2004-11-18 20:40 ` Ciaran McCreesh
2004-11-18 21:58 ` Robert Moss
2004-11-19 14:50 ` Ned Ludd
2004-11-20 8:17 ` [gentoo-dev] " Duncan
2004-11-21 21:10 ` Robert Moss [this message]
2004-11-22 9:54 ` [gentoo-dev] " Duncan
2004-11-22 4:22 ` [gentoo-dev] " Luke-Jr
2004-11-19 14:42 ` [gentoo-dev] " Brian Jackson
2004-11-19 22:00 ` Drake Wyrm
2004-11-19 23:31 ` Jason Stubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A10443.2070108@gentoo.org \
--to=robmoss@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox