Handle Python with non-default names

Check for python2/python3 and if found, pass them to --with-python.
Allow user to override the choice via a new config option. This
fixes systems where there is no "python", only "python2" or "python3".

Signed-off-by: Alexey Neyman <stilor@att.net>

1 files changed, 16 insertions, 0 deletions

diff --git a/config/debug/gdb.in.cross b/config/debug/gdb.in.cross
index 3053f713..e1935488 100644
--- a/config/debug/gdb.in.cross
+++ b/config/debug/gdb.in.cross
@@ -50,6 +50,22 @@ config GDB_CROSS_PYTHON
       have been reports of problems when linking gdb to the static
       libpython.a. This should be fixed in gdb >=7.3. YMMV.
 
+config GDB_CROSS_PYTHON_BINARY
+    string "Python binary to use"
+    depends on GDB_CROSS_PYTHON
+    help
+      The path to a binary passed to GDB configure. You may need to
+      specify this if Python is not available under the default name
+      (i.e. 'python'). By default, crosstool-NG will try python, python3
+      and python2, in that order.
+
+      To use this option in a canadian/cross-native build, you will
+      need to provide a helper script that will report the compilation
+      and linking flags for the host's Python, since configure script
+      will not be able to run the interpreter and query it. See the
+      help message in gdb's configure script for the --with-python option
+      for further guidance.
+
 config GDB_CROSS_EXTRA_CONFIG_ARRAY
     string
     prompt "Cross-gdb extra config"