public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <stilor@att.net>
To: electricworry <worryelectric@gmail.com>, crossgcc@sourceware.org
Subject: Re: Python and native gdb
Date: Fri, 20 Oct 2017 18:05:00 -0000	[thread overview]
Message-ID: <5d51a403-a37f-0c14-44e1-406b41006f34@att.net> (raw)
In-Reply-To: <CABZPTZRYAt85OyL29pXggC64f1d812C4AN06o-UpysP4egNF4Q@mail.gmail.com>

You'd need to have the Python libraries built for target first and a 
special script as explained in gdb/configure.ac's description of 
--with-python:

dnl There are several different values for --with-python:
....
dnl /path/to/python/executable -
dnl        Run python-config.py with this version of python to fetch the
dnl        compilation parameters.
dnl        NOTE: This needn't be the real python executable.
dnl        In a cross-compilation scenario (build != host), this could be
dnl        a shell script that provides what python-config.py provides for
dnl        --ldflags, --includes, --exec-prefix.

Crosstool-NG currently doesn't do that.

Regards,
Alexey.


On 10/20/2017 03:48 AM, electricworry wrote:
> Please could anyone advise, is it possible to build a Python enabled
> Native GDB similar to the Cross GDB option that exists in
> crosstool-ng?
>
> I've made a small change to 300-gdb.sh to add --with-python=python2
> for the native GDB build and I'm testing just now, so I guess I'll
> find out later today. But I'm thinking it's less trivial than that and
> there might be some extra work to be done. Am I right to be sceptical?
>
> Thanks.
>

      reply	other threads:[~2017-10-20 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 10:48 electricworry
2017-10-20 18:05 ` Alexey Neyman [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=5d51a403-a37f-0c14-44e1-406b41006f34@att.net \
    --to=stilor@att.net \
    --cc=crossgcc@sourceware.org \
    --cc=worryelectric@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).