mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Gdb debugging helper [PATCH]
Date: Fri, 11 Jan 2013 14:00:36 +0100	[thread overview]
Message-ID: <20130111130036.GC11738@pengutronix.de> (raw)
In-Reply-To: <CAOP6b3jb+sZpj0FmoQmSw0juM8zQum7+Zr7Pt9tAOHQuoZ=9Aw@mail.gmail.com>

On Fri, Jan 11, 2013 at 02:37:01PM +0200, Ruben Louw wrote:
> I'm trying to get my mind wrapped around this.
> 
> I ran your command and this is what it outputs:
> 
> Dynamic section at offset 0x3f1df8 contains 25 entries:
>   Tag        Type                         Name/Value
>  0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
>  0x0000000000000001 (NEEDED)             Shared library: [libncurses.so.5]
>  0x0000000000000001 (NEEDED)             Shared library: [libtinfo.so.5]
>  0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
>  0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
[...]
> its not linking to Python right?

Correct.

> if i then install python, do i have to
> make the link myself?

1. Install whatever packages provides Python.h in your distro (python-dev
   in Debian).

2. Rebuild the toolchain, or just part of if as Juergen suggested.
Python support is automatically enabled if 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

  parent reply	other threads:[~2013-01-11 13:00 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 [this message]
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=20130111130036.GC11738@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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