From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro_alves@portugalmail.pt>, gdb-patches@sourceware.org
Subject: Re: Windows DLL support update (a bit slimmer version)
Date: Fri, 12 Oct 2007 21:56:00 -0000 [thread overview]
Message-ID: <20071012215251.GA6302@caradoc.them.org> (raw)
In-Reply-To: <20071012213136.GG8721@adacore.com>
On Fri, Oct 12, 2007 at 02:31:36PM -0700, Joel Brobecker wrote:
> It looks like this change makes it necessary to have libexpat installed
> for DLLs support to work. Am I right? I'm looking for a simple way of
> avoiding this dependency, but I can't find any at the moment :-(.
Yes it does.
> Given the growing importance that XML is taking in GDB, maybe there
> will be a day when it is worth having a copy of the expat sources in
> GDB, and always build with expat.
I was told that importing expat was unacceptable. I was also told
that requiring it be installed to build GDB was unacceptable. This
is about the best I can manage given those restrictions.
Could you explain why you want to avoid expat? It's not like you have
to use a DLL version; it should not complicate shipping GDB at all.
It just has to be in CPPFLAGS and LDFLAGS when you're building GDB.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-12 21:53 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 [this message]
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
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=20071012215251.GA6302@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--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