This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Different flags for building plugins and gcc.
Hi Ian,
On 12 May 2010, at 21:00, Ian Lance Taylor wrote:
IainS <developer@sandoe-acoustics.co.uk> writes:
.. this seems a bit strange : -fPIC is not a ld flag...
LDFLAGS is flags that are passed to the compiler when linking. It is
not flags passed directly to the linker. I don't know why -fPIC is
there, but it shouldn't do any harm.
it's more that it's *not* force-added to CFLAGS that was a surprise -
since that's one thing the code says it's testing.
The Makefile fragment config/mh-ppc-darwin is selected in
configure.ac. I think the simplest approach would be to select
different config files based on whether --enable-plugins is used.
Agreed - it's the simplest .. but..
(a) that means we don't auto-detect the ability to use plugins - not a
major bind, but a shame.
(b) if we believe that the comment in mh-ppc-darwin is up to date, we
are sacrificing 3..5% compile performance if we build a compiler able
to use plugins.
.. (b) also applies to the other simple approach - just nuke mh-ppc-
darwin [which, incidentally, restores auto-detect of plugin
capability] ;-)
Iain