From: Kevin Buettner <kevinb@cygnus.com>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: Cross solib support; continued
Date: Tue, 06 Nov 2001 11:57:00 -0000 [thread overview]
Message-ID: <1011115185318.ZM1490@ocotillo.lan> (raw)
In-Reply-To: Orjan Friberg <orjan.friberg@axis.com> "Re: Cross solib support; continued" (Nov 15, 7:23pm)
On Nov 15, 7:23pm, Orjan Friberg wrote:
> > > That is, I would like a solib that is now searched for in
> > > solib-absolute-prefix to be searched for in solib-search-path instead.
> > > Would it make sense to add such a command, like solib-ignore-path? (I'd
> > > be happy to make it happen.) In effect, it would make all solibs to be
> > > searched for in solib-search-path by file name only, and
> > > solib-absolute-path would have no effect.
> >
> > Is this really necessary? I just put unstripped libraries in a
> > directory named lib and set the absolute prefix appropriately.
> >
> > Other than that, we should fall back to solib-search-path and the
> > basename if solib-absolute-path fails for us, IMO. Would that work for
> > you? Set the absolute-path to /dev/null or so and then add the
> > fallback code.
>
> FYI: I'm not twiddling my thumbs waiting for you or anybody else to
> implement this for me. I'm willing to dig in and do it, but I'm
> currently swamped in other things, and will probably be so for a few
> more days. As they say, "It's on my TODO list."
Good. Daniel's suggested approach to solving your problem sounds okay
to me so a patch based on his suggestion should be okay too.
Thanks,
Kevin
next prev parent reply other threads:[~2001-11-15 18:53 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BEAA3A0.586B3046@axis.com>
[not found] ` <20011108110955.A12240@nevyn.them.org>
2001-11-06 10:49 ` Orjan Friberg
2001-11-06 11:57 ` Kevin Buettner [this message]
2001-11-27 7:03 ` [RFC]: Solib search (Was: Re: Cross solib support; continued) Orjan Friberg
2001-11-14 12:49 ` Orjan Friberg
2001-11-27 7:12 ` Daniel Jacobowitz
2001-11-14 12:59 ` Daniel Jacobowitz
2001-11-14 13:21 ` Orjan Friberg
2001-11-14 13:53 ` Daniel Jacobowitz
2001-11-14 18:20 ` Orjan Friberg
2001-11-27 10:26 ` Orjan Friberg
2001-11-27 10:45 ` Daniel Jacobowitz
2001-11-14 18:28 ` Daniel Jacobowitz
2001-11-14 18:33 ` Orjan Friberg
2001-11-27 11:15 ` Orjan Friberg
2001-11-27 11:29 ` Daniel Jacobowitz
2001-11-14 18:55 ` Daniel Jacobowitz
2001-11-16 13:47 ` Orjan Friberg
2001-11-28 1:03 ` Orjan Friberg
2001-11-27 15:44 ` Kevin Buettner
2001-11-15 8:00 ` Kevin Buettner
2001-11-15 8:00 ` Daniel Jacobowitz
2001-11-15 9:16 ` Kevin Buettner
2001-11-27 16:00 ` Kevin Buettner
2001-11-27 15:47 ` Daniel Jacobowitz
2001-11-27 7:43 ` Daniel Jacobowitz
2001-11-27 7:36 ` Orjan Friberg
2001-11-27 8:00 ` Eli Zaretskii
2001-11-14 15:22 ` Eli Zaretskii
2001-11-27 10:16 ` Orjan Friberg
2001-11-14 18:14 ` Orjan Friberg
2001-11-14 20:58 ` Eli Zaretskii
2001-11-27 12:42 ` Eli Zaretskii
2001-11-28 0:55 ` Orjan Friberg
2001-11-16 13:24 ` Orjan Friberg
2001-11-28 2:00 ` Orjan Friberg
2001-11-16 14:02 ` Orjan Friberg
2001-11-17 2:18 ` Eli Zaretskii
2001-11-28 8:37 ` Eli Zaretskii
2001-11-28 9:43 ` Orjan Friberg
2001-11-17 4:03 ` Orjan Friberg
2001-11-17 12:37 ` Eli Zaretskii
2001-11-29 5:52 ` Orjan Friberg
2001-11-19 11:44 ` Orjan Friberg
2001-12-03 17:19 ` Kevin Buettner
2001-12-04 1:35 ` Orjan Friberg
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=1011115185318.ZM1490@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.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