mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gdb python support
Date: Fri, 23 Feb 2018 15:24:53 +0100	[thread overview]
Message-ID: <5410036.lbhQskFkj9@dabox> (raw)
In-Reply-To: <CAMwGMjzd0Txrxn3e-1KyuHy3_k8zN_=Vw2wZ4o+cTXOMbhJSGQ@mail.gmail.com>

Hi Jon

Am Freitag, 23. Februar 2018, 09:20:57 CET schrieb Jon Ringle:
> > > > > 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?
> > 
> > It's just a hack from a long time ago when the dependency handling was
> > broken. I just never bothered to change this. Patches are welcome.
> 
> I'd be happy to create a patch. Which way is preferable?
> 1) default --without-python and require an "opt-in" for
> --with-python=python3
> or
> 2) default --with-python=python3 and require an "opt-out" for
> --without-python
I would really prefer if no python would be opt out. Given that python 
scripting gets more and more important with gdb.

Best regards
Tim

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-02-23 14:25 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
2018-02-22 22:10     ` Michael Olbrich
2018-02-23 14:20       ` Jon Ringle
2018-02-23 14:24         ` Tim Sander [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=5410036.lbhQskFkj9@dabox \
    --to=tim@krieglstein.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