From: vichy <vichy.kuo@gmail.com>
To: loody <miloody@gmail.com>, binutils@sourceware.org
Subject: Re: Question about EXCLUDE FILE in ld script
Date: Wed, 22 Oct 2008 00:40:00 -0000 [thread overview]
Message-ID: <cd35b9e90810211739hc813a7egd9ee1aee3c56b354@mail.gmail.com> (raw)
In-Reply-To: <20081021220845.GL9946@bubble.grove.modra.org>
2008/10/22 Alan Modra <amodra@bigpond.net.au>:
> On Tue, Oct 21, 2008 at 10:33:22PM +0800, loody wrote:
>> *(EXCLUDE_FILE (*crtend.o *otherfile.o) .ctors)
>> will cause all .ctors sections from all files except 'crtend.o' and
>> 'otherfile.o' to be included. "
>>
>> My question is:
>> Why we have to use "*crtend.o" and "*otherfile.o" instead of
>> "crtend.o" and "otherfile.o".
>
> You don't need a wildcard here.
so, it is the rule about using EXCLUDE_FILE.
We have to add * in front of the file name we want to exclude.
If I am wrong, please let me know.
Sincerely Yours,
vichy
next prev parent reply other threads:[~2008-10-22 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 14:34 loody
2008-10-21 22:09 ` Alan Modra
2008-10-22 0:40 ` vichy [this message]
2009-05-13 8:46 ` loody
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=cd35b9e90810211739hc813a7egd9ee1aee3c56b354@mail.gmail.com \
--to=vichy.kuo@gmail.com \
--cc=binutils@sourceware.org \
--cc=miloody@gmail.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).