Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: brobecker@adacore.com, pedro_alves@portugalmail.pt,
	        gdb-patches@sourceware.org
Subject: Re: Windows DLL support update (a bit slimmer version)
Date: Sat, 13 Oct 2007 15:28:00 -0000	[thread overview]
Message-ID: <u3awfkt9n.fsf@gnu.org> (raw)
In-Reply-To: <20071013135220.GB22505@caradoc.them.org> (message from Daniel 	Jacobowitz on Sat, 13 Oct 2007 09:52:20 -0400)

> Date: Sat, 13 Oct 2007 09:52:20 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Joel Brobecker <brobecker@adacore.com>, pedro_alves@portugalmail.pt,
> 	gdb-patches@sourceware.org
> 
> On Sat, Oct 13, 2007 at 12:05:12PM +0200, Eli Zaretskii wrote:
> > > DLL support is pretty important in my opinion, and some users might
> > > be surprised to see it disappear silently because their system does
> > > not have libexpat installed.
> > 
> > Yes.  How about adding a warning message to GDB stating that lack of
> > libexpat causes the related feature to not work, when the user tries
> > to invoke a command that's affected?
> 
> Yes, this is done:
> 
>       warning (_("Can not parse XML library list; XML support was disabled "
>                  "at compile time"));

Then Joel, why do you say above ``disappear silently''?  Can you
describe a situation where this warning is not displayed?


  reply	other threads:[~2007-10-13 14:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19 22:06 Pedro Alves
2007-09-03 17:46 ` Daniel Jacobowitz
2007-09-05  8:46   ` Pedro Alves
2007-10-12 21:53   ` Joel Brobecker
2007-10-12 21:56     ` Daniel Jacobowitz
2007-10-12 22:54       ` Joel Brobecker
2007-10-13 13:51         ` Eli Zaretskii
2007-10-13 14:02           ` Daniel Jacobowitz
2007-10-13 15:28             ` Eli Zaretskii [this message]
2007-10-13 15:52               ` Joel Brobecker
2007-10-24 19:09           ` Daniel Jacobowitz
2007-10-24 20:12             ` Eli Zaretskii
2007-10-24 21:10               ` 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=u3awfkt9n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /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