On Tue, Jun 15, 2021 at 2:11 AM Michael Olbrich <[email protected]>
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
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to