On Tue, 23 Jan 2024 at 02:13, Dmitry Baryshkov <[email protected]> wrote:
>
> On Fri, 19 Jan 2024 at 14:43, Alexander Kanavin <[email protected]> 
> wrote:
> >
> > Despite our efforts to make static linking work, there have
> > been new reports of bizarre build failures:
> > https://lists.openembedded.org/g/openembedded-core/message/194006
> > https://lists.openembedded.org/g/openembedded-core/message/193907
> >
> > This commit changes back to dynamic linking, but places
> > the libraries in a custom location, per RP's suggestion.
> >
> > Signed-off-by: Alexander Kanavin <[email protected]>
>
> Alexander, please excuse my ignorance. What was the original issue
> that you observed on your build system? I tried simply reverting the
> offending commit and performing the build. I see libbsd, libattr and
> libmd populated in recipe-sysroot-native for both target and native
> builds that depend on shadow-native (added manual dependency of test
> -native recipe on shadow-native).

shadow contains executables for user/group management such as useradd.
These executables are used both in regular tasks and in setscene tasks
to create users that a recipe provides (in addition to simply
unpacking the sstate archive). It is those setscene tasks where
providing library dependencies of shadow is problematic. If you delete
tmp/ and run the build again from sstate, you'll see that for those
recipes which add users, shadow-native will be installed but those
three libraries will not. On some systems executing useradd will fall
through to using the build host libraries (which is a ticking time
bomb and can fail later), on others it will fail outright because e.g.
libbsd is not installed on the host.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194221): 
https://lists.openembedded.org/g/openembedded-core/message/194221
Mute This Topic: https://lists.openembedded.org/mt/103828721/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to