From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gdb python support
Date: Thu, 22 Feb 2018 15:57:32 -0500 [thread overview]
Message-ID: <CAMwGMjwwF8iA4sB5nU_fE7v_NRBb5qu3Q95+gSsmBpUwRD_rzg@mail.gmail.com> (raw)
In-Reply-To: <20180222203409.teh2ugnegphvp2dt@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]
On Thu, Feb 22, 2018 at 3:34 PM, Michael Olbrich <m.olbrich@pengutronix.de>
wrote:
> Hi,
>
> On Thu, Feb 22, 2018 at 02:05:03PM -0500, Jon Ringle wrote:
> > 3) I have `python-dev` package installed
>
> This should probably be python3-dev
>
> Ok
> > 4) rules/cross-gdb.make has the following, but I do not have
> > CROSS_GDB_WITHOUT_PYTHON set at all in my environment:
>
> Are you using build_all_v2.mk or build_one.sh? Then
> CROSS_GDB_WITHOUT_PYTHON is set to 'y' by default.
>
>
Ok. I see that there now. It would be nice if this default was consistent.
Reading the `cross-gdb.make` it appears that the default is with python,
but the `build_all_v2.mk` has the default the opposite. Can we pick a
default and stick to it?
Also. At this point, do I need to rebuild my whole toolchain again to get a
cross-gdb with python support, or can I get away with just doing:
$ ./p clean cross-gdb
$ CROSS_GDB_WITHOUT_PYTHON=n ./build_one.sh arm-v5te
-Jon
[-- Attachment #1.2: Type: text/html, Size: 1715 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-02-22 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 19:05 Jon Ringle
2018-02-22 20:34 ` Michael Olbrich
2018-02-22 20:57 ` Jon Ringle [this message]
2018-02-22 22:10 ` Michael Olbrich
2018-02-23 14:20 ` Jon Ringle
2018-02-23 14:24 ` Tim Sander
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=CAMwGMjwwF8iA4sB5nU_fE7v_NRBb5qu3Q95+gSsmBpUwRD_rzg@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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