On Fri, Oct 21, 2022 at 10:54 AM Alexander Kanavin
wrote:
>
> I think we had a similar problem in rust, and I ended up rewriting the
> shell script in python and running it with nativepython3 :-)
I had to re-write the script to be a C program because there wasn't
any way to make qemu find and
I think we had a similar problem in rust, and I ended up rewriting the
shell script in python and running it with nativepython3 :-)
Alex
On Fri, 21 Oct 2022 at 17:48, Joshua Watt wrote:
>
> Ya I've tracked it down to when qemu invokes the qemu-oe-bridge-helper
> to setup network bridging. This
Ya I've tracked it down to when qemu invokes the qemu-oe-bridge-helper
to setup network bridging. This is a shell script that uses /bin/sh, and
as the log indicates, /bin/sh can't find the required symbols to start
up (and qemu fails).
I also see it when runqemu attempt so to invoke the stty
This is the first time I hear about this - can you find out what is
expecting the symbol, and where it's supposed to come from?
Alex
On Fri, 21 Oct 2022 at 17:27, Joshua Watt wrote:
>
> This patch broke runqemu for me when I moved to kirkstone. I get this error:
>
> /bin/sh: symbol lookup
This patch broke runqemu for me when I moved to kirkstone. I get this error:
/bin/sh: symbol lookup error:
/grmn/prj/mrn/alchemy/build/tmp/eng/kirkstone/tetra/sysroots-uninative/x86_64-linux/lib/librt.so.1:
undefined symbol: __libc_unwind_link_get, version GLIBC_PRIVATE
And I'm not sure how to
On Sat, 12 Feb 2022 at 14:18, Enrico Scholz
wrote:
> | File: '.../meta/classes/qemuboot.bbclass', lineno: 141, function:
> do_write_qemuboot_conf
> | 0137:else:
> | 0138:val = d.getVar(k)
> | 0139:# we only want to write out relative paths so that we
"Alexander Kanavin" writes:
> --- a/meta/classes/qemuboot.bbclass
> +++ b/meta/classes/qemuboot.bbclass
> @@ -109,7 +109,7 @@ def qemuboot_vars(d):
> build_vars = ['MACHINE', 'TUNE_ARCH', 'DEPLOY_DIR_IMAGE',
> 'KERNEL_IMAGETYPE', 'IMAGE_NAME', 'IMAGE_LINK_NAME',
>
There's also an issue with the wrapper script run by host bash for
qemu-system that breaks with uninative, so just hold it off until I get it
all confirmed as working :)
Alex
On Sun, 6 Feb 2022 at 10:57, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sun, 2022-02-06 at 09:51
On Sun, 2022-02-06 at 09:51 +, Richard Purdie via lists.openembedded.org
wrote:
> On Sat, 2022-02-05 at 12:20 +, Richard Purdie via lists.openembedded.org
> wrote:
> > On Fri, 2022-02-04 at 21:40 +0100, Alexander Kanavin wrote:
> > > Some of the host distributions build the drivers in a
On Sat, 2022-02-05 at 12:20 +, Richard Purdie via lists.openembedded.org
wrote:
> On Fri, 2022-02-04 at 21:40 +0100, Alexander Kanavin wrote:
> > Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
> > that tricks uninative loader into loading pieces of the host libc, if
On Fri, 2022-02-04 at 21:40 +0100, Alexander Kanavin wrote:
> Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
> that tricks uninative loader into loading pieces of the host libc, if
> the same pieces haven't been previously loaded by native binaries. Mixing
> the two libc
The dynamic loader will print an error about missing libraries, but will
execute the binary regardless.
Alex
On Fri, 4 Feb 2022 at 22:17, Christopher Larson wrote:
> What will this do if uninative isn't enabled?
>
> On Fri, Feb 4, 2022 at 1:40 PM Alexander Kanavin
> wrote:
>
>> Some of the
What will this do if uninative isn't enabled?
On Fri, Feb 4, 2022 at 1:40 PM Alexander Kanavin
wrote:
> Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
> that tricks uninative loader into loading pieces of the host libc, if
> the same pieces haven't been previously
Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
that tricks uninative loader into loading pieces of the host libc, if
the same pieces haven't been previously loaded by native binaries. Mixing
the two libc versions leads to failures.
This change ensures that the correct
14 matches
Mail list logo
