From: PGNet Dev <pgnet.dev@gmail.com>
To: Christian Biesinger <cbiesinger@google.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 16:24:11 -0700 [thread overview]
Message-ID: <7191c88e-a7d8-6070-0e78-d8176f563bb1@gmail.com> (raw)
In-Reply-To: <CAPTJ0XEzTkXj4_kkqdnS3N8toqEB2x9DhVP-NMK23icjjVgWLA@mail.gmail.com>
On 3/25/20 3:55 PM, Christian Biesinger wrote:
>> export LDFLAGS="-L/usr/local/pyenv/versions/3.8-dev/lib"
>> (does this^ need to be rpath'd? need to poke around in here ...)
>
> If you can run python3.8, you probably already set things up correctly for that?
i 1st stumbled on this^ issue trying to run distro-pkg'd gdb in my pyenv.
it keeps insisting on hardcoded python pkg versions/paths that are the distro's default. annoying :-/
rpath with
export LDFLAGS="-L/usr/local/pyenv/versions/3.8-dev/lib -Wl,-rpath,/usr/local/pyenv/versions/3.8-dev/lib"
export LIBS="-lpython3.8"
is a better-safe-than-sorry choice; and shouldn't hurt
>> _does_ seem to get past the 'python unfound' problem, dropping me into the next issue ... which seems unrelated
>
> Yeah. Unfortunately I have no idea about that error, hopefully someone
> else can comment.
thx. i'll split off a new thread.
prev parent reply other threads:[~2020-03-25 23: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
2020-03-25 22:51 ` PGNet Dev
2020-03-25 22:55 ` Christian Biesinger
2020-03-25 23:24 ` PGNet Dev [this message]
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=7191c88e-a7d8-6070-0e78-d8176f563bb1@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
/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