From: Randy Witt <randy.e.witt@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [jethro][master][PATCH 1/1] uninative.bbclass: Choose the correct loader based on BUILD_ARCH
Date: Thu, 10 Dec 2015 14:12:45 -0800 [thread overview]
Message-ID: <5669F8DD.9010108@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbpvDC-NZrKkAmVMan17-DNLptSKUhagrPzA3LcundFNQ@mail.gmail.com>
On 12/10/2015 02:01 PM, Burton, Ross wrote:
> On 9 December 2015 at 20:50, Randy Witt <randy.e.witt@linux.intel.com>
> wrote:
>
>> -UNINATIVE_LOADER = "${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2"
>> +UNINATIVE_LOADER ?= "${@bb.utils.contains('BUILD_ARCH', 'x86_64',
>> '${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2',
>> '${STAGING_DIR_NATIVE}/lib/ld-linux.so.2', d)}"
>>
>
> Would it be neater, and more flexible when other arches are different
> (specifically I'm thinking of aarch64 here) to do:
>
> UNINATIVE_LOADER = "${STAGING_DIR_NATIVE}/lib/ld-linux.so.2"
> UNINATIVE_LOADER_x86-64 = "'${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2"
Yes, I like that better. I'll check the override and test it again.
> At least I think that overload is correct...
>
> Ross
>
next prev parent reply other threads:[~2015-12-10 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 20:50 [jethro][master][PATCH 0/1] Fix for 32-bit uninative Randy Witt
2015-12-09 20:50 ` [jethro][master][PATCH 1/1] uninative.bbclass: Choose the correct loader based on BUILD_ARCH Randy Witt
2015-12-10 22:01 ` Burton, Ross
2015-12-10 22:12 ` Randy Witt [this message]
2015-12-11 21:23 ` Burton, Ross
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=5669F8DD.9010108@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.