From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] problem configuring python3
Date: Tue, 15 Jun 2021 16:18:20 +0200 [thread overview]
Message-ID: <20210615141820.GD2340@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjxjrsXFa1LqQ7YqkdQh2tB227V08OTbeh=iUYKZuQLHyw@mail.gmail.com>
On Tue, Jun 15, 2021 at 10:13:58AM -0400, Jon Ringle wrote:
> On Tue, Jun 15, 2021 at 9:54 AM Michael Olbrich <m.olbrich@pengutronix.de>
> 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.olbrich@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.olbrich@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 (0x00007ffffb3b1000)
> > > libpython3.7m.so.1.0 =>
> > > /src/build/platform-ec1k/sysroot-host/bin/../lib/libpython3.7m.so.1.0
> > > (0x00007f0ccabe4000)
> > > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > > (0x00007f0ccaba0000)
> > > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > > (0x00007f0ccab7f000)
> > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x00007f0ccab7a000)
> > > libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > > (0x00007f0ccab75000)
> > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0cca9f2000)
> > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0cca82f000)
> > > /lib64/ld-linux-x86-64.so.2 (0x00007f0ccaef4000)
> > > jringle@-arm-v5te-linux-gnueabi:~/build$ ldd /usr/bin/python3.7
> > > linux-vdso.so.1 (0x00007ffd9bbf8000)
> > > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
> > > (0x00007f85dffc0000)
> > > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > > (0x00007f85dff9f000)
> > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x00007f85dff9a000)
> > > libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > > (0x00007f85dff95000)
> > > libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
> > > (0x00007f85dff58000)
> > > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f85dfd3a000)
> > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f85dfbb5000)
> > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f85df9f4000)
> > > /lib64/ld-linux-x86-64.so.2 (0x00007f85e0006000)
> >
> > 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
I'm out of ideas.
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
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-06-15 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMwGMjwgv1kQotakLPtFV_+_C4mSQQtfJ+EbrQrN5rQDaa=JtA@mail.gmail.com>
2021-06-15 6:10 ` Michael Olbrich
[not found] ` <CAMwGMjzYuSL0UkfU1YYG+wjw6bngL4Evjf5c9xSuDmwfxYyLZA@mail.gmail.com>
2021-06-15 12:08 ` Michael Olbrich
[not found] ` <CAMwGMjyVmD0Zc-swQjtBQcMXrQQNpBFAXuWWNY47nCDbNvvP9Q@mail.gmail.com>
2021-06-15 13:54 ` Michael Olbrich
[not found] ` <CAMwGMjxjrsXFa1LqQ7YqkdQh2tB227V08OTbeh=iUYKZuQLHyw@mail.gmail.com>
2021-06-15 14:18 ` Michael Olbrich [this message]
2021-06-16 6:56 ` Juergen Borleis
[not found] ` <CAMwGMjzH2AJt28G8xjX-PeknR2VLvU-RANv6yDSFodY=JNoeVA@mail.gmail.com>
2021-06-16 12:30 ` Juergen Borleis
[not found] ` <CAMwGMjyhwjtDN4oLMXN-fTDCrc+r0M65Li-tUhA2ZXoHQLe0tg@mail.gmail.com>
2021-06-16 13:02 ` Michael Olbrich
[not found] ` <CAMwGMjyM-fjWbRZGAsxYkY-FW_OgEoqD5rT9vjXiW2X6TPuCNw@mail.gmail.com>
2021-06-16 13:13 ` Juergen Borleis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210615141820.GD2340@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox