This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Specify python2 or python3 as Python program name
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jim Chen <nchen at mozilla dot com>
- Cc: gdb-patches at sourceware dot org, nchen at mozilla dot com
- Date: Thu, 12 May 2016 08:53:44 +0300
- Subject: Re: [PATCH] Specify python2 or python3 as Python program name
- Authentication-results: sourceware.org; auth=none
- References: <1463003507-13094-1-git-send-email-nchen at mozilla dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Jim Chen <nchen@mozilla.com>
> Cc: Jim Chen <nchen@mozilla.com>
> Date: Wed, 11 May 2016 17:51:46 -0400
>
> When initializing Python, GDB hard codes the Python program name to
> $prefix/bin/python, where $prefix is /usr for example. On some
> platforms, /usr/bin/python points to python3. So what happens is, even
> if GDB is built with python2 support, GDB ends up setting the Python
> program name to point to python3, causing a mismatch. I think it's
> better to deliberately specify python2 or python3.
I have Python 2.x installed, but there's no "python2" executable
anywhere in sight, only a "python" executable. Does this patch mean
GDB will no longer be able to invoke Python on my system?
Thanks.