From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E2787139083 for ; Tue, 5 Dec 2017 14:02:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4A904E0E2C; Tue, 5 Dec 2017 14:02:22 +0000 (UTC) Received: from smarthost03a.mail.zen.net.uk (smarthost03a.mail.zen.net.uk [212.23.1.20]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D86F9E0D1F for ; Tue, 5 Dec 2017 14:02:21 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03a.mail.zen.net.uk with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eMDng-0004u9-96 for gentoo-user@lists.gentoo.org; Tue, 05 Dec 2017 14:02:20 +0000 From: Peter Humphrey 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 Message-ID: <2838455.ohBBmiIvY4@peak> In-Reply-To: <21c92ebd-b79f-b1fa-f8b4-228e8aee5d07@gentoo.org> References: <20171203044339.egi6467qif26m7zi@solfire> <1808483.LPKLH7Qx5N@peak> <21c92ebd-b79f-b1fa-f8b4-228e8aee5d07@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03a-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: 52a8881c-30a9-49f9-87be-571855ac2e87 X-Archives-Hash: 0828ff383c76972df963854b9303da65 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.