From: Christian Biesinger <cbiesinger@google.com>
To: pgnet.dev@gmail.com
Cc: gdb@sourceware.org
Subject: Re: gdb/head build, --with-python=<path to working python> FAILs @ "no usable python found " ?
Date: Wed, 25 Mar 2020 17:24:05 -0500 [thread overview]
Message-ID: <CAPTJ0XHZXJswmHPK+LX3kA6-8V=knAXcY7hiAdyAk0asdpnGDg@mail.gmail.com> (raw)
In-Reply-To: <63388801-ba43-ecab-7384-c396515a32bc@gmail.com>
On Wed, Mar 25, 2020 at 5:14 PM PGNet Dev <pgnet.dev@gmail.com> wrote:
>
> On 3/25/20 2:57 PM, Christian Biesinger wrote:
> ...
> > Yes, Python 3 is known to work, though Python 2.7 is also supported.
>
> gr8, thx
>
> > - What does gdb/config.log say?
>
> ==> https://pastebin.com/ZPaKjG9Z
So the immediate problem is this:
configure:10601: checking for python
configure:10619: /usr/bin/gcc-10 -o conftest -O3 -Wall
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fmessage-length=0 -grecord-gcc-switches -march=native -mtune=native
-O3 -Wall -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fmessage-length=0 -grecord-gcc-switches
-march=native -mtune=native -D_FORTIFY_SOURCE=2
-I/usr/local/pyenv/versions/3.8-dev/include/python3.8
-I/usr/local/pyenv/versions/3.8-dev/include/python3.8 conftest.c
-lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm -Xlinker
-export-dynamic -lncursesw -lm -ldl >&5
/usr/lib64/gcc/x86_64-suse-linux/10/../../../../x86_64-suse-linux/bin/ld:
cannot find -lpython3.8
GDB uses basically this commandline to find the linker flags:
python3.8 ./gdb/python-config.py --ldflags
So I guess you'll either have to figure out why that does the wrong
thing (it seems to ask Python for the right values) or pass
LDFLAGS=/usr/local/pyenv/versions/3.8-dev/lib/ to configure.
Hope this helps,
Christian
>
>
>
> > - Do you also have the headers
>
> yep.
>
> ls -al /usr/local/pyenv/versions/3.8-dev/include/python3.8/Python.h
> -rw-r--r-- 1 root root 3.6K Mar 20 20:44 /usr/local/pyenv/versions/3.8-dev/include/python3.8/Python.h
> ... etc ...
>
> > and libraries installed?
>
> ls -al /usr/local/pyenv/versions/3.8-dev/lib/
> total 17M
> drwxr-xr-x 4 root root 4.0K Mar 20 20:44 ./
> drwxr-xr-x 7 root root 4.0K Mar 20 20:49 ../
> lrwxrwxrwx 1 root root 19 Mar 20 20:44 libpython3.8.so -> libpython3.8.so.1.0*
> -rwxr-xr-x 1 root root 17M Mar 20 20:44 libpython3.8.so.1.0*
> -rwxr-xr-x 1 root root 8.6K Mar 20 20:44 libpython3.so*
> drwxr-xr-x 2 root root 4.0K Mar 20 20:44 pkgconfig/
> drwxr-xr-x 35 root root 4.0K Mar 20 20:44 python3.8/
>
> atm, NO add'l *FLAGS set to either ...
>
> > - Just to confirm, /usr/local/pyenv/versions/3.8-dev/bin/python3.8 is the binary and not a directory, right?
>
> correct.
>
> ls -ald /usr/local/pyenv/versions/3.8-dev/bin/python3.8
> -rwxr-xr-x 1 root root 15K Mar 20 20:44 /usr/local/pyenv/versions/3.8-dev/bin/python3.8*
>
> /usr/local/pyenv/versions/3.8-dev/bin/python3.8 -V
> Python 3.8.2+
next prev parent reply other threads:[~2020-03-25 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 21:51 PGNet Dev
2020-03-25 21:57 ` Christian Biesinger
2020-03-25 22:14 ` PGNet Dev
2020-03-25 22:24 ` Christian Biesinger [this message]
2020-03-25 22:51 ` PGNet Dev
2020-03-25 22:55 ` Christian Biesinger
2020-03-25 23:24 ` PGNet Dev
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='CAPTJ0XHZXJswmHPK+LX3kA6-8V=knAXcY7hiAdyAk0asdpnGDg@mail.gmail.com' \
--to=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=pgnet.dev@gmail.com \
/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