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 [PATCH]
Date: Fri, 11 Jan 2013 14:30:20 +0200	[thread overview]
Message-ID: <CAOP6b3ip=EUOTsTmLg4xouNws9wCJWG4vpQk_sQPoJnGttO7tA@mail.gmail.com> (raw)
In-Reply-To: <9773402.Yor6vSR5Wv@dabox>


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

Hi Tim

I currently use 2012.12.0. I hd a look in cross-gdb.make, and the
--enable-python line is not there. So I added it. Do i have to rebuild the
toolchain after adding this line?

Thank you

Ruben

On Fri, Jan 11, 2013 at 2:27 PM, Tim Sander <tim@krieglstein.org> wrote:

> Hi Ruben
> > Thanks for the advice. Just to be sure. Python was not enabled (default)
> > then as the helper? Could it be I was correct? So then I need to rebuild
> > the toolchain, with Python enabled (example below)? Or is there a quick
> > hack for me to try without rebuilding the toolchain, cos then I have to
> > rebuild everything and I just want to quick test if this is the solution.
> It was not enabled for the older toolchains (2011.03.1) and is is enabled
> for
> 2011.11.3. Just take a look at rules/cross-gdb.make
>
> Best regards
> Tim
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>

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

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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-11 12:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  7:30 [ptxdist] Gdb debugging helper 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
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 [this message]
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='CAOP6b3ip=EUOTsTmLg4xouNws9wCJWG4vpQk_sQPoJnGttO7tA@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