From: IainS <developer@sandoe-acoustics.co.uk>
To: Ian Lance Taylor <iant@google.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: specs question.
Date: Mon, 12 Apr 2010 23:44:00 -0000 [thread overview]
Message-ID: <2750FD2B-E8CD-480A-B96E-CE4CF915E62C@sandoe-acoustics.co.uk> (raw)
In-Reply-To: <mcr7hoc1ckj.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
On 13 Apr 2010, at 00:22, Ian Lance Taylor wrote:
> IainS <developer@sandoe-acoustics.co.uk> writes:
>
>> yeah .. we use it in Darwin's dsymutil spec.
>>
>> %{!fdump=*:%{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S:\
>> %{.c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm: \
>> %{gdwarf-2:%{!gstabs*:%{!g0: dsymutil %{o*:%*}%{!
>> o:a.out}}}}}}}}}}}}"
>> %{!A:%{!nostdlib:%{!nostartfiles:%E}}} %{T*} %{F*} }}}}}}}\n"
>>
>>
>> if you put "-lm" on the c/l dsymutil doesn't get called.
>
> Note that in the specs language the %{.XXX: ...} is matched against
> the filename passed to the gcc driver. It doesn't know the source
> language of a .o file. So if you are linking, and passing .o files,
> then this approach won't work.
well, my first question to myself was 'why are there not ".o" and ".a"
in the list?' ;))
There are two aspects to this ...
1/ the fact that this is probably not the right thing to do in that
spec - easily solved by deleting it..
2/ The weird effect where putting -lm on the c/l causes the
substitution to fail - which hints at a deeper problem.
FWIW I couldn't (quickly) find any other spec using that syntax - so
perhaps it's not important.
cheers,
Iain
next prev parent reply other threads:[~2010-04-12 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 17:49 IainS
2010-04-12 22:30 ` Ian Lance Taylor
2010-04-12 22:41 ` IainS
2010-04-12 23:26 ` Ian Lance Taylor
2010-04-12 23:44 ` IainS [this message]
2010-04-13 0:01 ` Ian Lance Taylor
2010-04-13 8:55 ` IainS
2010-04-13 18:14 ` Peter O'Gorman
2010-04-13 19:21 ` IainS
2022-05-27 10:25 Iain Sandoe
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=2750FD2B-E8CD-480A-B96E-CE4CF915E62C@sandoe-acoustics.co.uk \
--to=developer@sandoe-acoustics.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).