https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65351
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #35249|0 |1
is obsolete| |
--- Comment #27 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 35255
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35255&action=edit
patch against 221916
Jakub's suggested approach to picflag.m4 seems reasonable.
AFAIK, the only place that GCC adds the flag is in mh-darwin which is now
checked.
If someone building GCC passes "-mdynamic-no-pic" on the command line for (say)
an i686-darwin12 native cross with clang as the compiler - then it will,
presumably, fail but that's something easy for the person doing the build to
rectify (and someone building native crosses is probably not a novice anyway)
checking on powerpc-darwin9 (GCC 5 bootstrap) x86_64-darwin12 (gcc 5 bootstrap)
x86_64-darwin13 (clang XCode6 bootstrap) i686-darwin10 (gcc-4.2.1 bootstrap).
