From: "Burton, Ross" <ross.burton@intel.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: Yocto Maillist <yocto@yoctoproject.org>,
Bradley Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: uninative support on non-x86 platforms
Date: Mon, 27 Jun 2016 15:29:15 +0100 [thread overview]
Message-ID: <CAJTo0LaPnJ=4A5qTfLMhU9EQvu21RaAWJgjCTj6275bv81AmLA@mail.gmail.com> (raw)
In-Reply-To: <20160623161806.GE20922@asimov.austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 23 June 2016 at 17:18, Patrick Williams <patrick@stwcx.xyz> wrote:
> Thanks. We will give it a try. I suspected there might be more to it than
> that
> based on this line:
>
> UNINATIVE_LOADER ?=
> "${STAGING_DIR}-uninative/${BUILD_ARCH}-linux/lib/${@bb.utils.contains('BUILD_ARCH',
> 'x86_64', 'ld-linux-x86-64.so.2', 'ld-linux.so.2', d)}"
>
>
> Which tag should we use to build this for publication?
>
> I was discussing with two of my colleagues and they mentioned that there
> is a free-for-opensource path to get a ppc64le virtual machine:
> http://osuosl.org/services/powerdev/request_hosting
> Would it be useful for us to set this up to build the uninative
> tarballs? I don't know what the process is for updating them for the
> x86 builds.
>
> It seems that the current autobuild runs on an x86 machine as well.
> Would there be any interest in a ppc64le slave?
>
For your own use, build a uninative-tarball using whatever commit of OE
you're using currently.
If it actually works and there's sufficient demand then it won't be
difficult to build it and add it to the poky configuration, but the main
requirement for that is that there is someone willing to fix any problems
that appear.
Ross
[-- Attachment #2: Type: text/html, Size: 1927 bytes --]
prev parent reply other threads:[~2016-06-27 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 16:43 uninative support on non-x86 platforms Patrick Williams
2016-06-22 20:00 ` Burton, Ross
2016-06-22 20:02 ` Burton, Ross
2016-06-23 16:18 ` Patrick Williams
2016-06-27 14:29 ` Burton, Ross [this message]
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='CAJTo0LaPnJ=4A5qTfLMhU9EQvu21RaAWJgjCTj6275bv81AmLA@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=patrick@stwcx.xyz \
--cc=yocto@yoctoproject.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 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.