This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, target] Sort out some issues in config{,/*}/darwin*.h
- From: Peter O'Gorman <peter at pogma dot com>
- To: IainS <developer at sandoe-acoustics dot co dot uk>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Mike Stump <mikestump at comcast dot net>, Dominique Dhumieres <dominiq at lps dot ens dot fr>, Jack Howarth <howarth at bromo dot med dot uc dot edu>
- Date: Thu, 15 Apr 2010 13:06:39 -0500
- Subject: Re: [Patch, target] Sort out some issues in config{,/*}/darwin*.h
- References: <7BF29134-0DF8-4621-8012-0935A5926970@sandoe-acoustics.co.uk>
On 04/14/2010 11:41 AM, IainS wrote:
> Hi all,
>
Hi Iain,
So I read all those PRs last night, and ick.
>
> o Split the LINK_COMMAND_SPEC into two bits:
> LINK_COMMAND_SPEC_A Common across the platform.
> DSYMUTIL_SPEC which needs to vary depending on the default debug
> format.
Looking at the PRs it does indeed seem absolutely necessary to wrap
dsymutil and always exit 0 from the wrapper... Why not eat all of its
stderr & stdout, btw, your -Wdsymutil flag could still be used to see
them if required?
> This latter step hopefully will get round the myriad "X.dSYM
> is directory" configury error msgs.
>
> - this now works for all FEs including fortran.
>
> o Filter out -lm and re-apply it where needed. [I've provided a
> bolt-hole for anyone who wants to
> force -lm (-force_lm) at least until we confirm that this is not
> an issue.]
If you do decide to remove -lm, there is no need to add a -force_lm
option, the users who really really want a libm can add it with its full
path. Also no need to not eat it when targetting 10.3 etc.
I think it's a horrible icky way to workaround the problem, but I don't
know that there exist less horrible ways. This really needs to be a
separate patch, just because it's so ugh.
I don't know what the -lgcc before -lSystem does, but ld won't look at
it until after it's looked at libSystem anyway, will it, unless the user
has passed -search_paths_first?
As for the other bits, well, they could be separate patches too,
couldn't they? :)
Peter