From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Emerge does want to tell me...what?
Date: Tue, 05 Dec 2017 14:02:19 +0000 [thread overview]
Message-ID: <2838455.ohBBmiIvY4@peak> (raw)
In-Reply-To: <21c92ebd-b79f-b1fa-f8b4-228e8aee5d07@gentoo.org>
On Tuesday, 5 December 2017 13:18:59 GMT Michael Orlitzky wrote:
> On 12/05/2017 05:23 AM, Peter Humphrey wrote:
> > I've been waiting for shouts of horror at that suggestion, but all's
> > quiet so I'll see if I can remember how to set -fpic in the environment
> > of palemoon. I'd have expected the ebuild do that though.
>
> The upstream build system should already be using -fpic for any of its
> shared objects[0]:
>
> The most important recommendation is to always use
> -fpic or -fPIC when generating code which ends up in
> DSOs. This applies to data as well as code... When gcc
> is used... It is therefore mandatory to compile all
> code which can potentially end up in a DSO with
> -fpic/-fPIC since otherwise the DSO might not work
> correctly.
>
> If -fpic is missing, it's probably a bug in some Makefile. The ebuild
> *can* fix that in the meantime, but it belongs upstream.
>
>
> [0] http://people.redhat.com/drepper/dsohowto.pdf
Ah. Right. I see now.
--
Regards,
Peter.
next prev parent reply other threads:[~2017-12-05 14:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 4:43 [gentoo-user] Emerge does want to tell me...what? tuxic
2017-12-03 5:16 ` Heiko Baums
2017-12-03 5:29 ` tuxic
2017-12-03 5:46 ` Heiko Baums
2017-12-03 6:28 ` Dale
2017-12-03 17:52 ` [gentoo-user] " Ian Zimmerman
2017-12-03 17:58 ` Simon Thelen
2017-12-03 20:06 ` Ian Zimmerman
2017-12-03 21:45 ` Simon Thelen
2017-12-03 22:57 ` [gentoo-user] palemoon and gcc [Was: Emerge does want to tell me...what?] Ian Zimmerman
2017-12-04 10:34 ` [gentoo-user] Re: Emerge does want to tell me...what? Peter Humphrey
2017-12-04 19:19 ` Walter Dnes
2017-12-04 19:30 ` Walter Dnes
2017-12-05 10:23 ` Peter Humphrey
2017-12-05 13:18 ` Michael Orlitzky
2017-12-05 14:02 ` Peter Humphrey [this message]
2017-12-05 16:52 ` Ian Zimmerman
2017-12-05 16:18 ` Peter Humphrey
2017-12-05 16:49 ` Raffaele Belardi
2017-12-06 10:11 ` Peter Humphrey
2017-12-06 10:33 ` Raffaele Belardi
2017-12-06 14:34 ` Peter Humphrey
2017-12-03 9:13 ` [gentoo-user] " Adam Carter
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=2838455.ohBBmiIvY4@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@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