On Wed, Jun 16, 2021 at 08:42:42AM -0400, Jon Ringle wrote:
> On Wed, Jun 16, 2021 at 8:30 AM Juergen Borleis <[email protected]> wrote:
> > Am Mittwoch, den 16.06.2021, 08:05 -0400 schrieb Jon Ringle:
> > > Am Dienstag, den 15.06.2021, 16:18 +0200 schrieb Michael Olbrich:
> > > > > […]
> > > > > I'm not sure why it would be looking for GLIBC_2.29
> > > >
> > > > It seems the used binary libm was linked against a newer version of
> > libc.
> > > >
> > > > Can you please send the output of
> > > >
> > > >  $ readelf -a
> > > > /src/build/platform-ec1k/sysroot-host/lib/libpython3.7m.so.1.0
> > > >
> > > > and
> > > >
> > > >  $ readelf -a /path/to/the/used/libm.so
> > > >
> > > >
> > > jringle@-arm-v5te-linux-gnueabi:~$ cat /usr/lib/x86_64-linux-gnu/libm.so
> > > /* GNU ld script
> > > */
> > > OUTPUT_FORMAT(elf64-x86-64)
> > > GROUP ( /lib/x86_64-linux-gnu/libm.so.6  AS_NEEDED (
> > > /usr/lib/x86_64-linux-gnu/libmvec_nonshared.a
> > > /lib/x86_64-linux-gnu/libmvec.so.1 ) )
> > >
> > > I will attach the output of
> > > $ readelf -a
> > /src/build/platform-ec1k/sysroot-host/lib/libpython3.7m.so.1.0
> > > and
> > > $ readelf -a /lib/x86_64-linux-gnu/libm.so.6
> > >
> > > as they are quite large.
> >
> > Sure :-)
> >
> > Its quite confusing. Your 'libm' hasn't any dependency to GLIBC_2.29, but
> > your
> > 'libpython3.7m' has. I had expect these version dependency came in via the
> > systems libm. Can you repeat the readelf command to your listed
> > 'libmvec.so.1'
> > and grep for the GLIBC_2.29 text? Something in this chain has exactly this
> > dependency to GLIBC_2.29.
> >
> >
> jringle@-arm-v5te-linux-gnueabi:~$ readelf -a
> /usr/lib/x86_64-linux-gnu/libmvec.a |grep GLIBC_2.29
> jringle@-arm-v5te-linux-gnueabi:~$ readelf -a
> /lib/x86_64-linux-gnu/libmvec.so.1 |grep GLIBC_2.29
> jringle@-arm-v5te-linux-gnueabi:~$ readelf -a
> /lib/x86_64-linux-gnu/libm.so.6 |grep GLIBC_2.29
> jringle@-arm-v5te-linux-gnueabi:~$ readelf -a
> /src/build/platform-ec1k/sysroot-host/lib/libpython3.7m.so.1.0|grep
> GLIBC_2.29
> 0000002b1a00  004000000007 R_X86_64_JUMP_SLO 0000000000000000 pow@GLIBC_2.29
> + 0
> 0000002b2300  007a00000007 R_X86_64_JUMP_SLO 0000000000000000 log@GLIBC_2.29
> + 0
> 0000002b4028  014d00000007 R_X86_64_JUMP_SLO 0000000000000000 exp@GLIBC_2.29
> + 0
>    64: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND pow@GLIBC_2.29
> (11)
>   122: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND log@GLIBC_2.29
> (11)
>   333: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND exp@GLIBC_2.29
> (11)
>  6880: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND pow@@GLIBC_2.29
>  7285: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND log@@GLIBC_2.29
>  8593: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND exp@@GLIBC_2.29
>  040:   b (GLIBC_2.29)    3 (GLIBC_2.2.5)   3 (GLIBC_2.2.5)   3
> (GLIBC_2.2.5)
>  078:   3 (GLIBC_2.2.5)   4 (GLIBC_2.2.5)   b (GLIBC_2.29)    3
> (GLIBC_2.2.5)
>  14c:   4 (GLIBC_2.2.5)   b (GLIBC_2.29)    f (GLIBC_2.2.5)   2 (GLIBC_2.3)
> 
>  0x0050:   Name: GLIBC_2.29  Flags: none  Version: 11

Did you build host-python3 in this container?

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to