Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: "Kevin Buettner" <kevinb@redhat.com>, <gdb@sources.redhat.com>
Subject: Re: GDB honouring RPATH in binaries.
Date: Thu, 20 Feb 2003 20:12:00 -0000	[thread overview]
Message-ID: <008d01c2d91c$59b4fba0$0202040a@catdog> (raw)
In-Reply-To: <20030220200536.GA21441@nevyn.them.org>

> On Thu, Feb 20, 2003 at 03:01:52PM -0500, Kris Warkentin wrote:
> > > > For remote targets, you must have solib-absolute-prefix set.
Searching
> > > > host libraries (whether found via RPATH or some other means) is
almost
> > > > invariably wrong.
> > >
> > > BTW, the sysroot stuff that Daniel recently added makes this
> > > a good deal less painful for the user.
> >
> > Not familiar with this.  Is there some documentation somewhere?
>
> It's in the GDB manual now, and it also applies to LD and GCC.  For GDB
> it only amounts to:
>
> You can set the default value of @samp{solib-absolute-prefix} by using
> the configure-time @samp{--with-sysroot} option.
>
> For GCC and LD it's a great deal more thorough; it changes header
> search paths, library search paths, etc.

Ah.  I can see how that would be useful.  We have an additional difficulty
in that we support multi-endian targets (mips, arm) so our
solib-absolute-prefix could change from $QNX_TARGET/armle to
$QNX_TARGET/armbe depending on the binary we load.  We already set up our
solib-search-path and s-a-p programmatically and I may have to expand that
logic further to make it all work correctly.

cheers,

Kris


  reply	other threads:[~2003-02-20 20:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 19:15 Kris Warkentin
2003-02-20 19:33 ` Kevin Buettner
2003-02-20 19:41   ` Daniel Jacobowitz
2003-02-20 19:44     ` Kris Warkentin
2003-02-20 19:48       ` Daniel Jacobowitz
2003-02-20 19:54         ` Kris Warkentin
2003-02-20 19:58           ` Kevin Buettner
2003-02-20 20:00             ` Kevin Buettner
2003-02-20 20:01               ` Kris Warkentin
2003-02-20 20:05                 ` Daniel Jacobowitz
2003-02-20 20:12                   ` Kris Warkentin [this message]
2003-02-20 20:04             ` Paul Koning
2003-02-20 20:10               ` Daniel Jacobowitz
2003-02-21 15:32                 ` Kris Warkentin
2003-02-21 18:28                   ` [Proposal] " Kris Warkentin
2003-02-21 18:30                   ` Kris Warkentin
2003-02-21 18:32                     ` Kris Warkentin
2003-02-21 19:14                     ` Kris Warkentin
2003-02-21 19:18                       ` Colin Burgess
2003-02-21 19:42                     ` Kevin Buettner
2003-02-21 19:46                       ` Colin Burgess
2003-02-21 19:55                       ` Kris Warkentin
2003-02-21 20:27                         ` Kris Warkentin
2003-02-21 21:02                           ` Kevin Buettner
2003-02-21 21:04                             ` Kris Warkentin
2003-02-20 20:18               ` Kevin Buettner
2003-02-20 20:00           ` Daniel Jacobowitz
2003-02-20 19:50     ` Kevin Buettner
2003-02-20 19:41   ` Kris Warkentin
2003-02-20 19:55     ` Kevin Buettner
2003-02-20 19:59       ` Kris Warkentin
2003-02-20 20:03         ` Daniel Jacobowitz
2003-02-20 19:48 ` Kevin Buettner
2003-02-20 19:52   ` Kris Warkentin

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='008d01c2d91c$59b4fba0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@redhat.com \
    /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