public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: binutils@sourceware.org
Subject: Re: RFC: allow a first "=" to mean sysroot for all paths in linker-scripts?
Date: Wed, 28 May 2014 13:26:00 -0000	[thread overview]
Message-ID: <201405281326.s4SDQPFn032138@ignucius.se.axis.com> (raw)
In-Reply-To: <201405270232.s4R2WUJL032457@ignucius.se.axis.com> (message from	Hans-Peter Nilsson on Tue, 27 May 2014 04:32:30 +0200)

Bump for the request for comments.
Also, tweaked bits in the TL;DR.

> From: Hans-Peter Nilsson <hp@axis.com>
> Date: Tue, 27 May 2014 04:32:30 +0200

> Is there a reason not to allow a first character '=' to mean
> sysroot-prefix for all paths inside linker scripts?  Today, it's
> interpreted that way for SEARCH_DIR, but elsewhere it's a syntax
> error.

(when not quoted)

>  GROUP ( /lib/libc.so.6 /lib/libc_nonshared.a  AS_NEEDED ( /lib/ld.so.1 ) )

(for those who didn't read the original post, the suggestion is to
allow "GROUP ( =/lib/libc.so.6 =/lib/libc_nonshared.a  AS_NEEDED ( =/lib/ld.so.1 ) )"
where the sysroot would be forced as opposed to "it depends".)

> For a non-sysrooted cross-toolchain you make the above line work
> by adjusting those paths manually in the installed script,
> prefixing with the installation prefix.

...but requires the sysroot be replicated within the sysroot
(e.g. by a parent-directory-chasing symlink) so your outermost
sysroot directory path component better not have a name-conflict
with a library. :)

brgds, H-P

  reply	other threads:[~2014-05-28 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27  2:32 Hans-Peter Nilsson
2014-05-28 13:26 ` Hans-Peter Nilsson [this message]
2014-06-09 13:56 ` Nicholas Clifton
2014-10-09  2:55   ` [PATCH 0/6] Allow a first "=" to mean sysroot for all paths in linker-scripts Hans-Peter Nilsson

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=201405281326.s4SDQPFn032138@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.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).