From: Ruben Louw <lfxciii@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Gdb debugging helper [PATCH]
Date: Fri, 11 Jan 2013 15:21:50 +0200 [thread overview]
Message-ID: <CAOP6b3gB-OADZ1zo-pQsgOXPvk+w_Ng0Bay8fE1U__UA+5k7aA@mail.gmail.com> (raw)
In-Reply-To: <CAOP6b3inXVTyn_TQ0qj=ehDdC2MgGW9s8XmW=6h=snRGQ3gt6Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
Nevermind my reply, I'll rebuild.
Thanks guys
On Fri, Jan 11, 2013 at 3:20 PM, Ruben Louw <lfxciii@gmail.com> wrote:
> So all I have to do is just install python-dev then right? it'll then pick
> everything up automatically.
>
>
> On Fri, Jan 11, 2013 at 3:18 PM, Michael Olbrich <m.olbrich@pengutronix.de
> > wrote:
>
>> Hi,
>>
>> On Fri, Jan 11, 2013 at 03:02:50PM +0200, Ruben Louw wrote:
>> > Thats what you meant by it installs it if it can find the headers,
>> right?
>> > so if i have python-dev installed on my host, and python is enabled in
>> > cross-gdb.make, then it will link python and all that, right?
>>
>> Actually, you don't need to modify cross-gdb.make. The rest is correct.
>>
>> 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: 2009 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-11 13:21 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
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 [this message]
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=CAOP6b3gB-OADZ1zo-pQsgOXPvk+w_Ng0Bay8fE1U__UA+5k7aA@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