On Wed, Aug 18, 2021 at 12:00 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> > hmm I am seeing pseudo build failures on master-next on all arches see
> > [1].  I wonder if this is related
> >
> > https://errors.yoctoproject.org/Errors/Details/601473/
>
> I think that would be an issue with my patch in master-next to try and fix
> other pseudo issues with 2.34 hosts.
>
> Basically we need pseudo to work with older glibc where the
> dlsym/dlvsym/dlerror
> functions are in libdl. This is because libpseudo may be loaded against
> host binaries
> which were not linked with glibc 2.34 but something older.
>
> To do that, we need to inject older versioning but the version to use is
> arch
> specific. I have a patch covering 32/64 bit x86 and arm but I haven't got
> further
> than that:
>
>
> ++#if defined (__aarch64__)
> ++#define DLSYMVER "2.17"
> ++#define DLSYMVER2 "2.17"
> ++#elif defined(__i386__)
> ++#define DLSYMVER "2.0"
> ++#define DLSYMVER2 "2.1"
> ++#else
> ++#define DLSYMVER "2.2.5"
> ++#define DLSYMVER2 "2.2.5"
> ++#endif
> ++
> ++__asm__(".symver dlerror,dlerror@GLIBC_" DLSYMVER);
> ++__asm__(".symver dlvsym,dlvsym@GLIBC_" DLSYMVER2);
> ++__asm__(".symver dlsym,dlsym@GLIBC_" DLSYMVER);
>
>
> I may need help finishing this off for other arches people are building it
> for. So far
> I was using this as a test to see if this would even work!


I think we should disable building pseudo for targets which are not used as
build hosts so essentially your patch is good with another addition of
compatible host string


>
> Cheers,
>
> Richard
>
>