From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Open bug overview: help wanted!
Date: Sat, 12 Jul 2014 20:54:30 -0500 [thread overview]
Message-ID: <20140712205430.1abdf0bf@core2quad.morethan.org> (raw)
In-Reply-To: <20140712215353.GD3582@free.fr>
On Sat, 12 Jul 2014 23:53:53 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > https://bugs.busybox.net/show_bug.cgi?id=7172 major
> > unassigned at buildroot.uclibc.org Name collision of rpath token
> > expansion and internal variables
> > The puzzle pieces for a solution are present in this bug report. All
> > it needs is someone caring enough to create a proper patch for this.
> > Any candidates?
>
> I'm not a fan of all this rpath trickery.
>
> Basically, the submitter (probably) wants this to run his
> buildroot-built system from somewhere else than / and does not want to
> chroot into it.
>
> Should we add complexity to Buildroot for this use-case?
>
Some members here in the past have expressed interest in supporting
after-market firmware creation for consumer devices.
Most have remained non-committal.
Buildroot does provide the string field for the end-user to pass
custom link-time options.
The point is, it should either work or be documented as to its
limitations.
That meets any definition of a "bug" in Buildroot.
Not a "unsupported use case", a "bug", as in "broke" by implementation".
I would be glad to fix it for you if I could.
Mike
next prev parent reply other threads:[~2014-07-13 1:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 18:50 [Buildroot] Open bug overview: help wanted! Thomas De Schampheleire
2014-07-12 20:12 ` Gustavo Zacarias
2014-07-16 17:08 ` Thomas De Schampheleire
2014-07-16 17:18 ` Gustavo Zacarias
2014-07-16 18:33 ` Thomas De Schampheleire
2014-07-12 21:53 ` Yann E. MORIN
2014-07-13 1:54 ` Mike Zick [this message]
2014-07-13 9:05 ` Yann E. MORIN
2014-07-13 13:29 ` Mike Zick
2014-07-13 14:56 ` Yann E. MORIN
2014-07-16 18:32 ` Thomas De Schampheleire
2014-07-15 19:27 ` Károly Kasza
2014-07-15 20:12 ` Thomas Petazzoni
2014-07-19 9:58 ` Károly Kasza
2014-07-16 15:00 ` Johan Oudinet
2014-07-16 7:31 ` Thomas Petazzoni
2014-07-16 18:35 ` Thomas De Schampheleire
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=20140712205430.1abdf0bf@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