On Fri, 19 Jan 2024 at 11:24, Richard Purdie
<richard.pur...@linuxfoundation.org> wrote:
> 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.

Sounds good. I'll make a patch for this.

Static linking in C world is something of an 'obsolete technology', it
isn't tested or supported by anyone really.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194028): 
https://lists.openembedded.org/g/openembedded-core/message/194028
Mute This Topic: https://lists.openembedded.org/mt/103661547/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to