From: Ian Lance Taylor <iant@google.com>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: <binutils@sourceware.org>
Subject: Re: division in ld scripts
Date: Wed, 09 Sep 2009 14:48:00 -0000 [thread overview]
Message-ID: <m37hw8uqbz.fsf@google.com> (raw)
In-Reply-To: <4AA7CBF202000078000141F9@vpn.id2.novell.com> (Jan Beulich's message of "Wed\, 09 Sep 2009 14\:38\:26 +0100")
"Jan Beulich" <JBeulich@novell.com> writes:
> Is it known/intended/documented that using the division operator (/) in
> ld scripts requires a blank to follow, at least in some cases (see below)?
> All other operators seem to behave as expected (apart from the missing
> but unlikely to be needed ^), while / results in a "syntax error" failure.
The linker language is kind of a mess. The problem here is that '/' can
appear in a file name, so the whole string gets picked up as a file name
rather than a number. I think it would be pretty hard to change without
breaking existing scripts.
Ian
next prev parent reply other threads:[~2009-09-09 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 13:38 Jan Beulich
2009-09-09 14:46 ` John Reiser
2009-09-09 14:48 ` Ian Lance Taylor [this message]
2009-09-09 14:59 ` Jan Beulich
2009-09-09 15:14 ` Ian Lance Taylor
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=m37hw8uqbz.fsf@google.com \
--to=iant@google.com \
--cc=JBeulich@novell.com \
--cc=binutils@sourceware.org \
/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).