mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] problem configuring python3
Date: Wed, 16 Jun 2021 15:02:01 +0200	[thread overview]
Message-ID: <20210616130201.GL22020@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjyhwjtDN4oLMXN-fTDCrc+r0M65Li-tUhA2ZXoHQLe0tg@mail.gmail.com>

On Wed, Jun 16, 2021 at 08:42:42AM -0400, Jon Ringle wrote:
> On Wed, Jun 16, 2021 at 8:30 AM Juergen Borleis <jbe@pengutronix.de> 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
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  parent reply	other threads:[~2021-06-16 13:02 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
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 [this message]
     [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=20210616130201.GL22020@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