From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] uninative: Add uninative - a way of reusing native/cross over multiple distros
Date: Thu, 28 Aug 2014 14:16:50 +0200 [thread overview]
Message-ID: <a88f1215-74bc-42bf-a221-55565b4ce8cf@email.android.com> (raw)
In-Reply-To: <1409221634.29296.134.camel@ted>
On 28 August 2014 12:27:14 CEST, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>These patches illustrate a new idea, a way of allowing a single set of
>cross/native sstate to work over multiple distros, even old ones.
>
>The assumption is that our own C library is basically up to date. We
>build
>and share a small tarball (~2MB) of a prebuilt copy of this along with
>a
>patchelf binary (which sadly is C++ based so libstdc++ is in there).
Begs for patchelf built against uClibc++ for the build.
Otherwise I like the idea!
Thanks,
next prev parent reply other threads:[~2014-08-28 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 10:27 [RFC PATCH] uninative: Add uninative - a way of reusing native/cross over multiple distros Richard Purdie
2014-08-28 12:16 ` Bernhard Reutner-Fischer [this message]
2014-10-08 14:58 ` Christopher Larson
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=a88f1215-74bc-42bf-a221-55565b4ce8cf@email.android.com \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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