Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2
Date: Fri, 19 Jan 2024 10:24:25 +0000	[thread overview]
Message-ID: <1fa0d9c93f89c4f486f5d7607b52bb55c18787e6.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8Wqm1NNx0VuxOU7sxoxsKcKh+vG-3WrkKiDqQVGSDNsg@mail.gmail.com>

On Fri, 2024-01-19 at 11:12 +0100, Alexander Kanavin wrote:
> I just tried poky master on ubuntu 20.04, and the issues do not
> appear. Do you have a custom setup?

There is another report about issues from the shadow static linking
change.

I'm worried that there are now accesses to files with are out of sight
of pseudo so that some combinations of builds are breaking. I'd
forgotten about pseudo in the push to fix the various sstate issues. It
is worrying we don't have good test cases for these.

I've also been thinking about how we could solve it. My proposal is
that we go back to dyanmic linking, however we add copies of the libs
we need into the shadow-native populate_sysroot sstate/sysroot output
in a special directory and we add that directory to the shadow binaries
as a RUNPATH/RPATH.

Cheers,

Richard






  reply	other threads:[~2024-01-19 10:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 13:15 [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2 Alexander Kanavin
2024-01-11 13:15 ` [PATCH v3 2/2] shadow: link executables statically for -native variant Alexander Kanavin
2024-01-17 12:46   ` [OE-core] " Dmitry Baryshkov
2024-01-18  9:50     ` Dmitry Baryshkov
2024-01-18  9:59     ` Richard Purdie
2024-01-18 10:13       ` Alexander Kanavin
2024-01-18 13:32         ` Dmitry Baryshkov
2024-01-18 13:37       ` Dmitry Baryshkov
2024-01-18 13:51         ` Richard Purdie
2024-01-18 15:12           ` Dmitry Baryshkov
2024-01-19  3:06 ` [OE-core] [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2 ChenQi
2024-01-19 10:12   ` Alexander Kanavin
2024-01-19 10:24     ` Richard Purdie [this message]
2024-01-19 10:44       ` Alexander Kanavin
2024-01-19 12:13     ` Chen, Qi
2024-01-19 12:24       ` Alexander Kanavin
2024-02-08 10:40         ` Vyacheslav Yurkov
2024-02-08 10:45           ` Alexander Kanavin
2024-02-08 10:52             ` Vyacheslav Yurkov
     [not found]             ` <17B1DDC9333F50F1.20876@lists.openembedded.org>
2024-02-08 12:11               ` Vyacheslav Yurkov
2024-02-08 12:16                 ` Richard Purdie
2024-02-08 13:09                   ` Vyacheslav Yurkov
2024-02-08 13:27                     ` Richard Purdie
2024-02-08 18:57                       ` Alexander Kanavin

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=1fa0d9c93f89c4f486f5d7607b52bb55c18787e6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --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