public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: -fPIC - Toolchain broken?
Date: Thu, 19 Oct 2006 20:33:26 +0000 (UTC)	[thread overview]
Message-ID: <eh8nem$cbe$2@sea.gmane.org> (raw)
In-Reply-To: 45374B67.6010901@getdesigned.at

Sebastian Redl <sebastian.redl@getdesigned.at> posted
45374B67.6010901@getdesigned.at, excerpted below, on  Thu, 19 Oct 2006
11:54:47 +0200:

> 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?

Yes.  Case in point is the very -fPIC we are discussing.  If the configure
tests -fPIC and due to a warning decides it can't be used, it doesn't
simply abort, but continues the process thru the rest of the config and
into the compile and linking.  Only later in the linking, and gets an error
similar to that of this thread because shared objects require -fPIC on
this platform, does it realize things went wrong.  Then the error it spits
out says to compile with -fPIC, when that's what it would have been doing
if the config hadn't misinterpreted an unrelated warning on the -fPIC test
as an indication that it shouldn't be used.

(The other half of your post addressed in the other subthread.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



      parent reply	other threads:[~2006-10-19 20:35 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
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 [this message]

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='eh8nem$cbe$2@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --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