mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ruben Louw <lfxciii@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Gdb debugging helper
Date: Fri, 11 Jan 2013 12:58:32 +0200	[thread overview]
Message-ID: <CAOP6b3ibgrbez+QmEs7th4ujtPfYzWxOV-ukrt+qFdJF5EJPZw@mail.gmail.com> (raw)
In-Reply-To: <20130111094206.GA11738@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 846 bytes --]

Hi Michael

I'd have to explicitly add Python to be built, or is it enabled by default?

Thanks

On Fri, Jan 11, 2013 at 11:42 AM, Michael Olbrich
<m.olbrich@pengutronix.de>wrote:

> Hi,
>
> On Fri, Jan 11, 2013 at 10:47:07AM +0200, Ruben Louw wrote:
> > hmm. makes sense to be on host. But I think this should be included when
> > build the toolchain or something,
>
> The gdb in OSELAT.Toolchain is built with python support if the Python
> headers are found.
>
> Michael
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>

[-- Attachment #1.2: Type: text/html, Size: 1493 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-11 10:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  7:30 Ruben Louw
2013-01-11  8:09 ` Juergen Beisert
2013-01-11  8:22   ` Ruben Louw
2013-01-11  8:40     ` Juergen Beisert
2013-01-11  8:47       ` Ruben Louw
2013-01-11  9:42         ` Michael Olbrich
2013-01-11 10:58           ` Ruben Louw [this message]
2013-01-11  9:42         ` [ptxdist] Gdb debugging helper [PATCH] Tim Sander
2013-01-11 10:57           ` Ruben Louw
2013-01-11 12:27             ` Tim Sander
2013-01-11 12:30               ` Ruben Louw
2013-01-11 12:45                 ` Juergen Beisert
2013-01-11 12:57                   ` Ruben Louw
2013-01-11 13:12                     ` Juergen Beisert
2013-01-11 13:16                       ` Ruben Louw
2013-01-11 13:25                         ` Juergen Beisert
2013-01-11 13:33                           ` Ruben Louw
2013-01-11 13:39                             ` Ruben Louw
2013-01-11 13:49                             ` Juergen Beisert
2013-01-11 12:30             ` Michael Olbrich
2013-01-11 12:37               ` Ruben Louw
2013-01-11 12:42                 ` Ruben Louw
2013-01-11 13:00                 ` Michael Olbrich
2013-01-11 13:02                   ` Ruben Louw
2013-01-11 13:18                     ` Michael Olbrich
2013-01-11 13:20                       ` Ruben Louw
2013-01-11 13:21                         ` Ruben Louw
2013-01-11 13: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=CAOP6b3ibgrbez+QmEs7th4ujtPfYzWxOV-ukrt+qFdJF5EJPZw@mail.gmail.com \
    --to=lfxciii@gmail.com \
    --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