public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Redl <sebastian.redl@getdesigned.at>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: -fPIC - Toolchain broken?
Date: Thu, 19 Oct 2006 11:54:47 +0200	[thread overview]
Message-ID: <45374B67.6010901@getdesigned.at> (raw)
In-Reply-To: <eh65t4$ig2$1@sea.gmane.org>

Duncan wrote:
> So... anytime I see this error, the first thing I try is flipping some
> CFLAGS on and off, and see if there's a reasonable combination that works.
>  Only if that fails do I try -fPIC and bug it as necessary.
>   
But wouldn't that apply only to errors that occur during the
configuration step? Or have you observed a situation where a compilation
change triggered by a failing non-essential test caused an error later?
> -fPIC is an interesting beast.  It's required on amd64 for all shared
> objects (*.so*), but isn't recommended (except for hardened) for
> application binaries, both due to occasional unexpected complications and
> because it's slower.  Thus, putting it in CFLAGS is NOT a good thing,
> unless it's for a specific library package only, to get it to merge while
> you are waiting for the bug you filed on it (right?) to get
> researched/fixed/tested.
>   
Speaking of which, is there any way to configure flags per package?
Something like /etc/portage/package.flags, where I can configure CFLAGS,
CXXFLAGS and LDFLAGS?

Sebastian Redl
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-10-19  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:08 [gentoo-amd64] -fPIC - Toolchain broken? Sebastian Redl
2006-10-18 15:28 ` Hemmann, Volker Armin
2006-10-18 15:53 ` Simon Stelling
2006-10-18 16:08   ` Simon Stelling
2006-10-18 17:41   ` Sebastian Redl
2006-10-18 18:32     ` Simon Stelling
2006-10-18 21:21 ` [gentoo-amd64] " Duncan
2006-10-19  9:54   ` Sebastian Redl [this message]
2006-10-19 13:11     ` Conway S. Smith
2006-10-19 15:42       ` Simon Stelling
2006-10-19 20:43         ` Duncan
2006-10-20  9:10           ` Simon Stelling
2006-10-23 14:20           ` Kevin F. Quinn
2006-10-23 15:22             ` Duncan
2006-10-19 20:33     ` Duncan

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=45374B67.6010901@getdesigned.at \
    --to=sebastian.redl@getdesigned.at \
    --cc=gentoo-amd64@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