Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Nick Clifton <nickc@redhat.com>
Cc: DJ Delorie <dj@delorie.com>,
	gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: What to do with info addr and location expressions
Date: Tue, 22 Jul 2003 15:39:00 -0000	[thread overview]
Message-ID: <20030722153748.GA26839@nevyn.them.org> (raw)
In-Reply-To: <m37k6a37g0.fsf@redhat.com>

On Tue, Jul 22, 2003 at 04:30:23PM +0100, Nick Clifton wrote:
> Hi DJ,
> 
> >> > DJ replied:
> >> > bfd/ perhaps?
> >> 
> >> Except that that then ruins the plan that readelf should be buildable
> >> without libbfd.a.
> >
> > Don't build it with libbfd.  Just keep it in the same directory.
> > There's no rule that says we can only have one library per directory.
> 
> Doh!  Yes, I should have realised that.
> 
> But that does mean that GDB would need the bfd/ sources, not just an
> installed libbfd.a.  Is this OK with the GDB guys ?  If so, then I
> have no objections.

GDB's already dependent on libbfd - and will probably stay that way.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-22 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 14:54 Elena Zannoni
2003-07-18 15:30 ` Daniel Jacobowitz
2003-07-18 15:50   ` Andrew Cagney
2003-07-21 11:14     ` Nick Clifton
2003-07-21 17:54       ` Jim Blandy
2003-07-21 19:12         ` Andrew Cagney
2003-07-21 20:07         ` Nick Clifton
2003-07-21 20:14           ` Daniel Berlin
2003-07-21 20:35             ` Doug Evans
2003-07-21 20:33           ` Andrew Cagney
2003-07-21 20:45             ` DJ Delorie
2003-07-22  9:20               ` Nick Clifton
2003-07-22 13:26                 ` DJ Delorie
2003-07-22 15:33                   ` Nick Clifton
2003-07-22 15:39                     ` Daniel Jacobowitz [this message]
2003-07-18 16:01   ` Elena Zannoni
2003-07-18 16:11     ` Daniel Jacobowitz

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=20030722153748.GA26839@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@delorie.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickc@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