From: Khem Raj <raj.khem@gmail.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Enabling uninative by default in oe-core?
Date: Thu, 17 Nov 2016 15:19:25 -0800 [thread overview]
Message-ID: <0cc6e1e2-aeca-b999-5123-768cac5213b8@gmail.com> (raw)
In-Reply-To: <CAP71WjwJDTVsAcU9YrVh0uBcQ87Xt6HB9fCuj_t-jHcaGsjEWw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2675 bytes --]
On 11/17/16 10:56 AM, Nicolas Dechesne wrote:
> On Thu, Nov 17, 2016 at 7:06 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> Background: uninative is a class that downloads a precompiled host glibc for
>>> use in the sysroot, thus isolating the native sysroot from the host
>>> environment. This means greater sstate reuse, as instead of native builds
>>> being dependent on the host system they're able to be shared between all
>>> hosts. There is a reference tarball hosted on www.yoctoproject.org
>>> <http://www.yoctoproject.org>, and the URL can be overridden by distros if you
>>> would prefer to build your own.
>>>
>>> We enable this in Poky so that we get greater reuse on the autobuilders, and
>>> due to some issues with the C++ ABI the eSDK generation in master now requires
>>> uninative to be enabled. The question is: do we now enable uninative by
>>> default in oe-core's nodistro (pointing at the yoctoproject tarball), or do we
>>> keep it disabled by default and require the user to enable uninative if they
>>> wish to build an eSDK?
>>>
>>> Personally I'm torn: I don't like eSDK not working out of the box, but I don't
>>> really like oe-core nodistro depending on uninative. Though enabling
>>> uninative globally does mean everything works out of the box, so following the
>>> principle of Least Surprise that's what we should do.
>>
>> If we are supporing e-SDK in OE-Core then we should enable uninative too
>> on the same lines.
>>
>> It does improve the user experience so I am in favor of adding it
>> unconditionally. May be tarball can be hosted on oe mirrors as well for
>> redundancy
>
>
> I am not sure how people would care about that (yet ;-) but uninative
> does not work for arm64 (host).
>
> Build Configuration:
> BB_VERSION = "1.32.0"
> BUILD_SYS = "aarch64-linux"
> NATIVELSBSTRING = "Debian-8.6"
> TARGET_SYS = "arm-oe-linux-gnueabi"
> MACHINE = "qemuarm"
> DISTRO = "nodistro"
> DISTRO_VERSION = "nodistro.0"
> TUNE_FEATURES = "arm armv5 thumb dsp"
> TARGET_FPU = "soft"
> meta = "master:9303d8055c45a0f6af295d70a6f6a8b9d8d8a7c9"
>
> ERROR: Uninative selected but not configured correctly, please set
> UNINATIVE_CHECKSUM[aarch64]
>
> I don't know much about it, but it would be nice to fix that before we
> enable it by default. I will try to have a look at it more closely..
>
Someone with aarch64 hardware in build boxes could take that up. I dont think
yocto project or many community members have access to hardware. I would be
happy if it informed me and continues without uninative.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-11-17 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:31 Enabling uninative by default in oe-core? Burton, Ross
2016-11-17 18:06 ` Khem Raj
2016-11-17 18:50 ` [Openembedded-architecture] " Denys Dmytriyenko
2016-11-17 23:22 ` Khem Raj
2016-11-17 18:56 ` Nicolas Dechesne
2016-11-17 23:19 ` Khem Raj [this message]
2016-11-17 21:47 ` [Openembedded-architecture] " Mark Hatle
2016-11-18 7:15 ` Koen Kooi
2016-11-18 8:03 ` [Openembedded-architecture] " Richard Purdie
2016-11-18 16:28 ` akuster808
2016-11-18 18:06 ` [Openembedded-architecture] " Richard Purdie
2016-11-18 20:50 ` Koen Kooi
2016-11-18 21:17 ` Denys Dmytriyenko
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=0cc6e1e2-aeca-b999-5123-768cac5213b8@gmail.com \
--to=raj.khem@gmail.com \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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