Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7172] Name collision of rpath token expansion and internal variables
Date: Sun, 29 Jun 2014 14:46:38 -0500	[thread overview]
Message-ID: <20140629144638.66b520d4@core2quad.morethan.org> (raw)
In-Reply-To: <20140629131427.2A9F19CFC7@busybox.osuosl.org>

On Sun, 29 Jun 2014 13:14:27 +0000 (UTC)
bugzilla at busybox.net wrote:

> https://bugs.busybox.net/show_bug.cgi?id=7172
> 
> --- Comment #13 from Thomas De Schampheleire
> <patrickdepinguin@gmail.com> 2014-06-29 13:14:26 UTC --- Mike, 
> 
> Would you care to send patches to the mailing list to implement these
> changes? In a first step, the 'Now' comment, 
>

The 'Now" comment is just a text message edit -
that is within my paygrade to handle.  ;)

And maybe an addition to the "known bugs" in the manual.
I think this one will be around for a long time.

> and then the alternative
> you proposed. Having the changes on the mailing list will facilitate
> the discussion and review, as few developers look at the bug comments.
> 

The "fix" (work-a-round) of assigning the output of a:
 "printf '%s' '$' 'ORIGIN' ... "
I was using, was in a post image build script (outside of Buildroot).
(I no longer need an '$ORIGIN' - changed my planning to not need it.)

I don't know the "Make" equivalent, nor where in the infrastructure
the change needs to be made.

Something way outside of my paygrade I am afraid.

That will have to wait for someone very familiar with the BR
infrastructure to have a long lasting attack of boredom and
free time.

Mike
> Thanks, Thomas
> 

  reply	other threads:[~2014-06-29 19:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08  2:41 [Buildroot] [Bug 7172] New: Name collision of rpath token expansion and internal variables bugzilla at busybox.net
2014-06-08  7:03 ` [Buildroot] [Bug 7172] " bugzilla at busybox.net
2014-06-08 10:38   ` Mike Zick
2014-06-08 11:24     ` Samuel Martin
2014-06-08 12:57       ` Mike Zick
2014-06-08 13:53         ` Thomas Petazzoni
2014-06-08 14:04 ` bugzilla at busybox.net
2014-06-08 14:21 ` bugzilla at busybox.net
2014-06-08 15:56 ` bugzilla at busybox.net
2014-06-08 16:03 ` bugzilla at busybox.net
2014-06-08 16:28 ` bugzilla at busybox.net
2014-06-08 16:48 ` bugzilla at busybox.net
2014-06-08 18:18 ` bugzilla at busybox.net
2014-06-08 18:20 ` bugzilla at busybox.net
2014-06-10 12:40 ` bugzilla at busybox.net
2014-06-11 21:36 ` bugzilla at busybox.net
2014-06-22 13:52 ` bugzilla at busybox.net
2014-06-22 13:52 ` bugzilla at busybox.net
2014-06-29 13:14 ` bugzilla at busybox.net
2014-06-29 19:46   ` Mike Zick [this message]
2014-07-07 13:06 ` bugzilla at busybox.net
2014-07-17 18:00 ` bugzilla at busybox.net
2014-07-30 20:15 ` bugzilla at busybox.net
2014-07-30 22:41 ` bugzilla at busybox.net
2014-08-01 17:22 ` bugzilla at busybox.net

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=20140629144638.66b520d4@core2quad.morethan.org \
    --to=minimod@morethan.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox