Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Implement qXfer:libraries for Linux/gdbserver
Date: Tue, 09 Aug 2011 18:25:00 -0000	[thread overview]
Message-ID: <CAN9gPaGFQvMKLBAWewdEugPBkGaqM_ZMAJAZ9QoNbOVguKY_dg@mail.gmail.com> (raw)
In-Reply-To: <20110808212412.GB19337@host1.jankratochvil.net>

On Mon, Aug 8, 2011 at 5:24 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> I do not think it is any problem to require + bundle libexpat, there was even
> some FAQ of people with broken GDB for ARM remote targets before some proper
> error messages were added indicating libexpat is missing for GDB.

You may want to go through the archives on this topic; there were
considerable reasons not to bundle libexpat when I introduced the
dependency.

-- 
Thanks,
Daniel


  reply	other threads:[~2011-08-09 18:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 18:11 [patch] Implement qXfer:libraries for Linux/gdbserver [Was: Re: [RFC] Make target_read_string faster over high-latency links.] Paul Pluzhnikov
2011-08-08 18:36 ` Jan Kratochvil
2011-08-08 18:56   ` Paul Pluzhnikov
2011-08-08 21:24     ` [patch] Implement qXfer:libraries for Linux/gdbserver Jan Kratochvil
2011-08-09 18:25       ` Daniel Jacobowitz [this message]
2011-08-08 21:10 ` Jan Kratochvil
2011-08-08 21:31   ` Paul Pluzhnikov
2011-08-08 21:38     ` Jan Kratochvil
2011-08-08 23:50       ` Paul Pluzhnikov
2011-08-09  9:07         ` Jan Kratochvil
2011-08-09 16:57           ` Paul Pluzhnikov
2011-08-14 16:36             ` Jan Kratochvil
2011-10-03 21:57               ` IMO-obsolste: " Jan Kratochvil

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=CAN9gPaGFQvMKLBAWewdEugPBkGaqM_ZMAJAZ9QoNbOVguKY_dg@mail.gmail.com \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=ppluzhnikov@google.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