From: "Adrian Bunk" <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: chris.laplante@agilent.com, Martin Jansa <martin.jansa@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Uninative for i386 native tool?
Date: Mon, 20 Apr 2020 17:52:11 +0300 [thread overview]
Message-ID: <20200420145211.GA2315@localhost> (raw)
In-Reply-To: <207860401ddfafd8de45143986549873935deff7.camel@linuxfoundation.org>
On Sun, Apr 19, 2020 at 11:15:55PM +0100, Richard Purdie wrote:
> On Sun, 2020-04-19 at 21:58 +0000, Chris Laplante via
> lists.openembedded.org wrote:
> > One possible work around which I'm using for some prebuilt native
> > binaries is to call them with hosts loader (e.g. /lib32/ld-linux.so.2
> > ${STAGING_BINDIR_NATIVE}/my-tool params)
> >
> > Ooh, nice. Thanks for the tip! Definitely curious about a longer-term
> > workaround but this is good for the short term.
>
> I suspect uninative assumes all binaries are for the main system
> architecture so its probably trying to change the interpreter to a 64
> bit one which clearly won't work in this case.
>
> It would be a question of stopping it for these binaries somehow...
uninative is default but optional, would
INHERIT_remove = "uninative"
solve this problem?
> Cheers,
>
> Richard
cu
Adrian
prev parent reply other threads:[~2020-04-20 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 21:37 Uninative for i386 native tool? Chris Laplante
2020-04-19 21:49 ` [OE-core] " Martin Jansa
2020-04-19 21:58 ` Chris Laplante
2020-04-19 22:15 ` Richard Purdie
2020-04-20 13:56 ` Chris Laplante
2020-04-20 14:03 ` Richard Purdie
2020-04-20 15:15 ` Chris Laplante
2020-04-20 15:24 ` Richard Purdie
[not found] ` <16078BB604B2F7AB.6073@lists.openembedded.org>
2020-04-20 14:00 ` Chris Laplante
2020-04-20 14:52 ` Adrian Bunk [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=20200420145211.GA2315@localhost \
--to=bunk@stusta.de \
--cc=chris.laplante@agilent.com \
--cc=martin.jansa@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 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.