From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: Joerg Faschingbauer <jfasch@aon.at>
Cc: charlet@ACT-Europe.FR, rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: Use of -fPIC on Tru64
Date: Tue, 18 Dec 2001 14:03:00 -0000 [thread overview]
Message-ID: <20011218225647.A9739@dublin.int.act-europe.fr> (raw)
In-Reply-To: <20011218205324C.jfasch@aon.at>; from jfasch@aon.at on Tue, Dec 18, 2001 at 08:53:24PM +0100
> The message I replied to was something along "There are
> implementations where you do not need PIC to load a shared library, so
> there is no need to require PIC". You didn't say anything about Tru64
> (though you did in a previous message), and I was nitpicking. Kind of.
Well obviousely this is non very helpful and non constructive, since the
subject line of this thread couldn't be clearer. Also if I were to
nitpick, I would say that you didn't read the message you quoted very carefully
because I said "shared library", and not "dynamic library", but I won't.
I guess if noone answered that nobody is really interested in discussing it.
I still haven got a clear answer as to why this change has been made in GCC.
Was it a deliberate choice, or a general change ?
As a result of this change, we can no longer rely on LIBGCC2_FLAGS to build
other shared libraries in GCC (e.g for GNAT) in a simple way on Tru64, which
is inconvenient, but I guess unavoidable.
So let me phrase my question differently: is there a configure flag/setting
that can be reused in Makefiles to know whether a target absolutely
needs -fPIC to build a shared library ?
Arno
next prev parent reply other threads:[~2001-12-18 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 1:35 Arnaud Charlet
2001-12-13 1:44 ` Richard Henderson
2001-12-13 3:35 ` Arnaud Charlet
2001-12-13 9:26 ` Richard Henderson
2001-12-13 9:40 ` Arnaud Charlet
2001-12-13 9:49 ` Richard Henderson
2001-12-13 9:57 ` Arnaud Charlet
2001-12-17 11:54 ` Joerg Faschingbauer
2001-12-17 15:22 ` Arnaud Charlet
2001-12-18 12:12 ` Joerg Faschingbauer
2001-12-18 14:03 ` Arnaud Charlet [this message]
2001-12-18 12:45 ` Jeff Sturm
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=20011218225647.A9739@dublin.int.act-europe.fr \
--to=charlet@act-europe.fr \
--cc=gcc@gcc.gnu.org \
--cc=jfasch@aon.at \
--cc=rth@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).