All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v2] toolchain: linker options with a $ sign are not supported
Date: Thu, 31 Jul 2014 23:54:03 +0200	[thread overview]
Message-ID: <20140731235403.0d3d5baa@free-electrons.com> (raw)
In-Reply-To: <4340ac304e166f70044180b7d49eb6e43828eace.1406760999.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Thu, 31 Jul 2014 00:57:15 +0200, Yann E. MORIN wrote:
> As reported in bug #7172 [0], setting BR2_TARGET_LDFLAGS to a value
> containing a $ sign can lead to unexpected results.
> 
> This is because it is very hard to know when the $ sign gets evaluated:
>   - in the Buildroot-level make
>   - in the shell called by the Buildroot-level make
>   - in the package's own build-system, either at configure time, in the
>     Makefile, in a shell in the Makefile...
> 
> So, it is very difficult to know how much escaping that would need.
> 
> A proposal is to use a shell variable to pass such values unmolested.
> But it is not that simple either, since it still contains a $ sign, and
> there is not much certainty as to when it would be evaluated.
> 
> Instead, just document this limitation, both in the help text for
> BR2_TARGET_LDFLAGS, and in the known-issues section in the manual.
> 
> Does not really fix #7172, but at least the limitation is documented.
> 
> [0] https://bugs.buildroot.org/show_bug.cgi?id=7172
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Mike Zick <minimod@morethan.org>
> ---
>  docs/manual/known-issues.txt  | 4 ++++
>  toolchain/toolchain-common.in | 3 +++
>  2 files changed, 7 insertions(+)

Applied, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-07-31 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 22:57 [Buildroot] [PATCH 0/2 v2] Workaround for bug #7172: patchelf (branch yem/patchelf) Yann E. MORIN
2014-07-30 22:57 ` [Buildroot] [PATCH 1/2 v2] toolchain: linker options with a $ sign are not supported Yann E. MORIN
2014-07-31  6:38   ` Thomas De Schampheleire
2014-07-31 21:54   ` Thomas Petazzoni [this message]
2014-07-30 22:57 ` [Buildroot] [PATCH 2/2 v2] package/patchelf: new host package Yann E. MORIN
2014-07-31  3:26   ` Baruch Siach
2014-07-31  6:41   ` Thomas De Schampheleire
2014-07-31 21:55   ` Thomas Petazzoni
2014-07-31 22:05     ` Yann E. MORIN

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=20140731235403.0d3d5baa@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.