Re: [ptxdist] problem configuring python3
Am Mittwoch, den 16.06.2021, 09:10 -0400 schrieb Jon Ringle: > […] > I think your question led to the root cause. It looks like host-python3 was > pulled from a -dev.tar.gz package since logfile doesn't show the > prepare/compile stages. The dev package must have been built in a different > environment that had glibc 2.29 "User error: insert more coffee"? ;-) Jürgen -- Pengutronix e.K. | Juergen Borleis | Steuerwalder Str. 21 | https://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-128 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9| ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Wed, Jun 16, 2021 at 9:02 AM Michael Olbrich wrote: > > Did you build host-python3 in this container? > > $ grep host-python3\\. platform-ec1k/logfile target: host-python3.6bcbacf952d0391d7b67701a157ca622.srchash finished target host-python3.6bcbacf952d0391d7b67701a157ca622.srchash target: host-python3.get finished target host-python3.get target: host-python3.bd7ce9b162cd4dad598cb606d4df85ee.cfghash finished target host-python3.bd7ce9b162cd4dad598cb606d4df85ee.cfghash target: host-python3.install.unpack finished target host-python3.install.unpack target: host-python3.extract finished target host-python3.extract target: host-python3.report finished target host-python3.report target: host-python3.install.post finished target host-python3.install.post I think your question led to the root cause. It looks like host-python3 was pulled from a -dev.tar.gz package since logfile doesn't show the prepare/compile stages. The dev package must have been built in a different environment that had glibc 2.29 -Jon ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Wed, Jun 16, 2021 at 08:42:42AM -0400, Jon Ringle wrote: > On Wed, Jun 16, 2021 at 8:30 AM Juergen Borleis 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 > 002b1a00 0047 R_X86_64_JUMP_SLO pow@GLIBC_2.29 > + 0 > 002b2300 007a0007 R_X86_64_JUMP_SLO log@GLIBC_2.29 > + 0 > 002b4028 014d0007 R_X86_64_JUMP_SLO exp@GLIBC_2.29 > + 0 >64: 0 FUNCGLOBAL DEFAULT UND pow@GLIBC_2.29 > (11) > 122: 0 FUNCGLOBAL DEFAULT UND log@GLIBC_2.29 > (11) > 333: 0 FUNCGLOBAL DEFAULT UND exp@GLIBC_2.29 > (11) > 6880: 0 FUNCGLOBAL DEFAULT UND pow@@GLIBC_2.29 > 7285: 0 FUNCGLOBAL DEFAULT UND log@@GLIBC_2.29 > 8593: 0 FUNCGLOBAL 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- | ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Wed, Jun 16, 2021 at 8:30 AM Juergen Borleis wrote: > Hi Jon, > > 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 002b1a00 0047 R_X86_64_JUMP_SLO pow@GLIBC_2.29 + 0 002b2300 007a0007 R_X86_64_JUMP_SLO log@GLIBC_2.29 + 0 002b4028 014d0007 R_X86_64_JUMP_SLO exp@GLIBC_2.29 + 0 64: 0 FUNCGLOBAL DEFAULT UND pow@GLIBC_2.29 (11) 122: 0 FUNCGLOBAL DEFAULT UND log@GLIBC_2.29 (11) 333: 0 FUNCGLOBAL DEFAULT UND exp@GLIBC_2.29 (11) 6880: 0 FUNCGLOBAL DEFAULT UND pow@@GLIBC_2.29 7285: 0 FUNCGLOBAL DEFAULT UND log@@GLIBC_2.29 8593: 0 FUNCGLOBAL 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 -Jon ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
Hi Jon, 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. Jürgen -- Pengutronix e.K. | Juergen Borleis | Steuerwalder Str. 21 | https://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-128 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9| ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
Hi Jon, 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 Jürgen -- Pengutronix e.K. | Juergen Borleis | Steuerwalder Str. 21 | https://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-128 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9| ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 10:13:58AM -0400, Jon Ringle wrote:
> On Tue, Jun 15, 2021 at 9:54 AM Michael Olbrich
> wrote:
> > On Tue, Jun 15, 2021 at 08:17:36AM -0400, Jon Ringle wrote:
> > > On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich <
> > m.olbr...@pengutronix.de>
> > > wrote:
> > > > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote:
> > > > > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich <
> > > > m.olbr...@pengutronix.de>
> > > > > wrote:
> > > > > > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote:
> > > > > > > It seems like I'm having a problem with python3.7m in
> > sysroot-host
> > > > trying
> > > > > > > to use the host libm. I'm not sure if the issue is with ptxdist
> > or
> > > > with
> > > > > > the
> > > > > > > docker container image I use for building the ptxdist bsp.
> > > > > > >
> > > > > > > ---
> > > > > > > target: python3.prepare
> > > > > > > ---
> > > > > > >
> > > > > > > checking for git... found
> > > > > > > checking build system type... x86_64-host-linux-gnu
> > > > > > > checking host system type... arm-v5te-linux-gnueabi
> > > > > > > checking for python3.7... python3.7
> > > > > > > checking for python interpreter for cross build... python3.7:
> > > > > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found
> > > > (required
> > > > > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l
> > > > > > > ibpython3.7m.so.1.0)
> > > > > >
> > > > > > This looks strange. I think it's trying to execute
> > > > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That
> > > > should
> > > > > > not happen. Can you execute that manually?
> > > > > > For some reason the glibc that is used does not match the libm from
> > > > your
> > > > > > system. Maybe there is a version mismatch in the docker container?
> > > > > >
> > > > > >
> > > > > I fails in the same way executing manually within a ptxdist bash
> > shell:
> > > > > [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$
> > > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7:
> > > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found
> > (required
> > > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3
> > > > > .7m.so.1.0)
> > > >
> > > > What's the output of
> > > >
> > > > $ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > > > $ ldd /usr/bin/python3.7
> > > >
> > > >
> > > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd
> > > /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > > /src/build/platform-ec1k/sysroot-host/bin/python3.7:
> > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required
> > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3
> > > .7m.so.1.0)
> > >
> > >linux-vdso.so.1 (0x7b3b1000)
> > >libpython3.7m.so.1.0 =>
> > > /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3.7m.so.1.0
> > > (0x7f0ccabe4000)
> > >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > > (0x7f0ccaba)
> > >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > > (0x7f0ccab7f000)
> > >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x7f0ccab7a000)
> > >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > > (0x7f0ccab75000)
> > >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0cca9f2000)
> > >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0cca82f000)
> > >/lib64/ld-linux-x86-64.so.2 (0x7f0ccaef4000)
> > > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /usr/bin/python3.7
> > >linux-vdso.so.1 (0x7ffd9bbf8000)
> > >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > > (0x7f85dffc)
> > >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > > (0x7f85dff9f000)
> > >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x7f85dff9a000)
> > >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > > (0x7f85dff95000)
> > >libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
> > > (0x7f85dff58000)
> > >libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f85dfd3a000)
> > >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f85dfbb5000)
> > >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f85df9f4000)
> > >/lib64/ld-linux-x86-64.so.2 (0x7f85e0006000)
> >
> > This looks ok. What about:
> >
> > $ ls -l /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6
> >
> >
> jringle@-arm-v5te-linux-gnueabi:~/build$ ls -l
> /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6
> lrwxrwxrwx 1 root root 12 May 1 2019 /lib/x86_64-linux-gnu/libc.so.6 ->
> libc-2.28.so
>
> lrwxrwxrwx 1 root root 12 May 1 2019 /lib/x86_64-linux-gnu/libm.so.6 ->
> libm-2.28.so
>
> jringle@-arm-v5te-linux-gnueabi:~/build$ ls -l
> /lib/x86_64-linux-gnu/lib{c,m}-*
>
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 9:54 AM Michael Olbrich
wrote:
> On Tue, Jun 15, 2021 at 08:17:36AM -0400, Jon Ringle wrote:
> > On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich <
> m.olbr...@pengutronix.de>
> > wrote:
> > > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote:
> > > > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich <
> > > m.olbr...@pengutronix.de>
> > > > wrote:
> > > > > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote:
> > > > > > It seems like I'm having a problem with python3.7m in
> sysroot-host
> > > trying
> > > > > > to use the host libm. I'm not sure if the issue is with ptxdist
> or
> > > with
> > > > > the
> > > > > > docker container image I use for building the ptxdist bsp.
> > > > > >
> > > > > > ---
> > > > > > target: python3.prepare
> > > > > > ---
> > > > > >
> > > > > > checking for git... found
> > > > > > checking build system type... x86_64-host-linux-gnu
> > > > > > checking host system type... arm-v5te-linux-gnueabi
> > > > > > checking for python3.7... python3.7
> > > > > > checking for python interpreter for cross build... python3.7:
> > > > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found
> > > (required
> > > > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l
> > > > > > ibpython3.7m.so.1.0)
> > > > >
> > > > > This looks strange. I think it's trying to execute
> > > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That
> > > should
> > > > > not happen. Can you execute that manually?
> > > > > For some reason the glibc that is used does not match the libm from
> > > your
> > > > > system. Maybe there is a version mismatch in the docker container?
> > > > >
> > > > >
> > > > I fails in the same way executing manually within a ptxdist bash
> shell:
> > > > [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$
> > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7:
> > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found
> (required
> > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3
> > > > .7m.so.1.0)
> > >
> > > What's the output of
> > >
> > > $ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > > $ ldd /usr/bin/python3.7
> > >
> > >
> > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd
> > /src/build/platform-ec1k/sysroot-host/bin/python3.7
> > /src/build/platform-ec1k/sysroot-host/bin/python3.7:
> > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required
> > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3
> > .7m.so.1.0)
> >
> >linux-vdso.so.1 (0x7b3b1000)
> >libpython3.7m.so.1.0 =>
> > /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3.7m.so.1.0
> > (0x7f0ccabe4000)
> >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > (0x7f0ccaba)
> >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f0ccab7f000)
> >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7f0ccab7a000)
> >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > (0x7f0ccab75000)
> >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0cca9f2000)
> >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0cca82f000)
> >/lib64/ld-linux-x86-64.so.2 (0x7f0ccaef4000)
> > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /usr/bin/python3.7
> >linux-vdso.so.1 (0x7ffd9bbf8000)
> >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > (0x7f85dffc)
> >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f85dff9f000)
> >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7f85dff9a000)
> >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > (0x7f85dff95000)
> >libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
> > (0x7f85dff58000)
> >libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f85dfd3a000)
> >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f85dfbb5000)
> >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f85df9f4000)
> >/lib64/ld-linux-x86-64.so.2 (0x7f85e0006000)
>
> This looks ok. What about:
>
> $ ls -l /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6
>
>
jringle@-arm-v5te-linux-gnueabi:~/build$ ls -l
/lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6
lrwxrwxrwx 1 root root 12 May 1 2019 /lib/x86_64-linux-gnu/libc.so.6 ->
libc-2.28.so
lrwxrwxrwx 1 root root 12 May 1 2019 /lib/x86_64-linux-gnu/libm.so.6 ->
libm-2.28.so
jringle@-arm-v5te-linux-gnueabi:~/build$ ls -l
/lib/x86_64-linux-gnu/lib{c,m}-*
-rwxr-xr-x 1 root root 1824496 May 1 2019 /lib/x86_64-linux-gnu/
libc-2.28.so
-rw-r--r-- 1 root root 1579448 May 1 2019 /lib/x86_64-linux-gnu/
libm-2.28.so
I'm not sure why it would be looking for GLIBC_2.29
-Jon
___
ptxdist mailing list
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 08:17:36AM -0400, Jon Ringle wrote: > On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich > wrote: > > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote: > > > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich < > > m.olbr...@pengutronix.de> > > > wrote: > > > > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > > > > > It seems like I'm having a problem with python3.7m in sysroot-host > > trying > > > > > to use the host libm. I'm not sure if the issue is with ptxdist or > > with > > > > the > > > > > docker container image I use for building the ptxdist bsp. > > > > > > > > > > --- > > > > > target: python3.prepare > > > > > --- > > > > > > > > > > checking for git... found > > > > > checking build system type... x86_64-host-linux-gnu > > > > > checking host system type... arm-v5te-linux-gnueabi > > > > > checking for python3.7... python3.7 > > > > > checking for python interpreter for cross build... python3.7: > > > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found > > (required > > > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l > > > > > ibpython3.7m.so.1.0) > > > > > > > > This looks strange. I think it's trying to execute > > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That > > should > > > > not happen. Can you execute that manually? > > > > For some reason the glibc that is used does not match the libm from > > your > > > > system. Maybe there is a version mismatch in the docker container? > > > > > > > > > > > I fails in the same way executing manually within a ptxdist bash shell: > > > [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$ > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7: > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 > > > .7m.so.1.0) > > > > What's the output of > > > > $ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7 > > $ ldd /usr/bin/python3.7 > > > > > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd > /src/build/platform-ec1k/sysroot-host/bin/python3.7 > /src/build/platform-ec1k/sysroot-host/bin/python3.7: > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 > .7m.so.1.0) > >linux-vdso.so.1 (0x7b3b1000) >libpython3.7m.so.1.0 => > /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3.7m.so.1.0 > (0x7f0ccabe4000) >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x7f0ccaba) >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f0ccab7f000) >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ccab7a000) >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 > (0x7f0ccab75000) >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0cca9f2000) >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0cca82f000) >/lib64/ld-linux-x86-64.so.2 (0x7f0ccaef4000) > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /usr/bin/python3.7 >linux-vdso.so.1 (0x7ffd9bbf8000) >libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x7f85dffc) >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f85dff9f000) >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f85dff9a000) >libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 > (0x7f85dff95000) >libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 > (0x7f85dff58000) >libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f85dfd3a000) >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f85dfbb5000) >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f85df9f4000) >/lib64/ld-linux-x86-64.so.2 (0x7f85e0006000) This looks ok. What about: $ ls -l /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6 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- | ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 8:08 AM Michael Olbrich wrote: > On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote: > > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich < > m.olbr...@pengutronix.de> > > wrote: > > > > > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > > > > It seems like I'm having a problem with python3.7m in sysroot-host > trying > > > > to use the host libm. I'm not sure if the issue is with ptxdist or > with > > > the > > > > docker container image I use for building the ptxdist bsp. > > > > > > > > --- > > > > target: python3.prepare > > > > --- > > > > > > > > checking for git... found > > > > checking build system type... x86_64-host-linux-gnu > > > > checking host system type... arm-v5te-linux-gnueabi > > > > checking for python3.7... python3.7 > > > > checking for python interpreter for cross build... python3.7: > > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found > (required > > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l > > > > ibpython3.7m.so.1.0) > > > > > > This looks strange. I think it's trying to execute > > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That > should > > > not happen. Can you execute that manually? > > > For some reason the glibc that is used does not match the libm from > your > > > system. Maybe there is a version mismatch in the docker container? > > > > > > > > I fails in the same way executing manually within a ptxdist bash shell: > > [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$ > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 > > /src/build/platform-ec1k/sysroot-host/bin/python3.7: > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 > > .7m.so.1.0) > > What's the output of > > $ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7 > $ ldd /usr/bin/python3.7 > > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7 /src/build/platform-ec1k/sysroot-host/bin/python3.7: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 .7m.so.1.0) linux-vdso.so.1 (0x7b3b1000) libpython3.7m.so.1.0 => /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3.7m.so.1.0 (0x7f0ccabe4000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7f0ccaba) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0ccab7f000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ccab7a000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f0ccab75000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0cca9f2000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0cca82f000) /lib64/ld-linux-x86-64.so.2 (0x7f0ccaef4000) jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /usr/bin/python3.7 linux-vdso.so.1 (0x7ffd9bbf8000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7f85dffc) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f85dff9f000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f85dff9a000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f85dff95000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7f85dff58000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f85dfd3a000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f85dfbb5000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f85df9f4000) /lib64/ld-linux-x86-64.so.2 (0x7f85e0006000) ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 07:16:32AM -0400, Jon Ringle wrote: > On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich > wrote: > > > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > > > It seems like I'm having a problem with python3.7m in sysroot-host trying > > > to use the host libm. I'm not sure if the issue is with ptxdist or with > > the > > > docker container image I use for building the ptxdist bsp. > > > > > > --- > > > target: python3.prepare > > > --- > > > > > > checking for git... found > > > checking build system type... x86_64-host-linux-gnu > > > checking host system type... arm-v5te-linux-gnueabi > > > checking for python3.7... python3.7 > > > checking for python interpreter for cross build... python3.7: > > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l > > > ibpython3.7m.so.1.0) > > > > This looks strange. I think it's trying to execute > > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That should > > not happen. Can you execute that manually? > > For some reason the glibc that is used does not match the libm from your > > system. Maybe there is a version mismatch in the docker container? > > > > > I fails in the same way executing manually within a ptxdist bash shell: > [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$ > /src/build/platform-ec1k/sysroot-host/bin/python3.7 > /src/build/platform-ec1k/sysroot-host/bin/python3.7: > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 > .7m.so.1.0) What's the output of $ ldd /src/build/platform-ec1k/sysroot-host/bin/python3.7 $ ldd /usr/bin/python3.7 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- | ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich wrote: > On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > > It seems like I'm having a problem with python3.7m in sysroot-host trying > > to use the host libm. I'm not sure if the issue is with ptxdist or with > the > > docker container image I use for building the ptxdist bsp. > > > > --- > > target: python3.prepare > > --- > > > > checking for git... found > > checking build system type... x86_64-host-linux-gnu > > checking host system type... arm-v5te-linux-gnueabi > > checking for python3.7... python3.7 > > checking for python interpreter for cross build... python3.7: > > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l > > ibpython3.7m.so.1.0) > > This looks strange. I think it's trying to execute > /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That should > not happen. Can you execute that manually? > For some reason the glibc that is used does not match the libm from your > system. Maybe there is a version mismatch in the docker container? > > I fails in the same way executing manually within a ptxdist bash shell: [ptx] jringle@-arm-v5te-linux-gnueabi:~/build$ /src/build/platform-ec1k/sysroot-host/bin/python3.7 /src/build/platform-ec1k/sysroot-host/bin/python3.7: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3 .7m.so.1.0) Running the system's python3.7 works fine: jringle@-arm-v5te-linux-gnueabi:~/build$ which python3.7 /usr/bin/python3.7 jringle@-arm-v5te-linux-gnueabi:~/build$ python3.7 Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> -Jon ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
Re: [ptxdist] problem configuring python3
On Mon, Jun 14, 2021 at 05:57:36PM -0400, Jon Ringle wrote: > It seems like I'm having a problem with python3.7m in sysroot-host trying > to use the host libm. I'm not sure if the issue is with ptxdist or with the > docker container image I use for building the ptxdist bsp. > > --- > target: python3.prepare > --- > > checking for git... found > checking build system type... x86_64-host-linux-gnu > checking host system type... arm-v5te-linux-gnueabi > checking for python3.7... python3.7 > checking for python interpreter for cross build... python3.7: > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required > by /src/build/platform-ec1k/sysroot-host/bin/../lib/l > ibpython3.7m.so.1.0) This looks strange. I think it's trying to execute /src/build/platform-ec1k/sysroot-host/bin/python3.7 and fails. That should not happen. Can you execute that manually? For some reason the glibc that is used does not match the libm from your system. Maybe there is a version mismatch in the docker container? Michael > > 'python3' must depend on 'host-system-python3' for 'python3'! > > > 'python3' must depend on 'host-system-python / host-system-python3' for > 'python'! > > configure: error: python3.7 interpreter not found > > -Jon > ___ > ptxdist mailing list > ptxdist@pengutronix.de > To unsubscribe, send a mail with subject "unsubscribe" to > ptxdist-requ...@pengutronix.de -- 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- | ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
[ptxdist] problem configuring python3
It seems like I'm having a problem with python3.7m in sysroot-host trying to use the host libm. I'm not sure if the issue is with ptxdist or with the docker container image I use for building the ptxdist bsp. --- target: python3.prepare --- checking for git... found checking build system type... x86_64-host-linux-gnu checking host system type... arm-v5te-linux-gnueabi checking for python3.7... python3.7 checking for python interpreter for cross build... python3.7: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /src/build/platform-ec1k/sysroot-host/bin/../lib/l ibpython3.7m.so.1.0) 'python3' must depend on 'host-system-python3' for 'python3'! 'python3' must depend on 'host-system-python / host-system-python3' for 'python'! configure: error: python3.7 interpreter not found -Jon ___ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
