This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: python config question

From: Michael Snyder <msnyder at vmware dot com>
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, Michael Snyder <msnyder at vmware dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Wed, 03 Mar 2010 09:46:12 -0800
Subject: Re: python config question
References: <4B8C5DD4.1070501@vmware.com> <20100302052219.GF2850@adacore.com> <4B8D54E1.7030003@vmware.com> <20100303045039.GB15364@adacore.com> <20100303092047.GA24396@host0.dyn.jankratochvil.net> <20100303152913.GA18518@caradoc.them.org>

Daniel Jacobowitz wrote:

On Wed, Mar 03, 2010 at 10:20:47AM +0100, Jan Kratochvil wrote:

IIUC you ship libpython*.so.* libraries bundled with the shipped gdb.
Isn't ld.so's $ORIGIN useful?

$ORIGIN and rpath


FYI, this is how we do it, and part of why I don't think automatic
-rpath is a good idea.


You're saying that you ship the python library, install it in the
same directory as gdb, and get the runtime loader to look for it there?

References:
- python config question
  - From: Michael Snyder
- Re: python config question
  - From: Joel Brobecker
- Re: python config question
  - From: Michael Snyder
- Re: python config question
  - From: Joel Brobecker
- Re: python config question
  - From: Jan Kratochvil
- Re: python config question
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]