From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Add expat to the GDB sources
Date: Mon, 24 Jul 2006 00:15:00 -0000 [thread overview]
Message-ID: <20060724001529.GA20102@nevyn.them.org> (raw)
In-Reply-To: <200607232318.k6NNIV28004376@elgar.sibelius.xs4all.nl>
On Mon, Jul 24, 2006 at 01:18:31AM +0200, Mark Kettenis wrote:
> Depending on an external expat package comes with the additional
> maintenance cost of testing the detection code and handling additional
> bug reports from people who can't build gdb because of problems with
> expat.
I don't think this is a high cost, I really don't. We should document
our own requirements clearly. If we have requirements that themselves
have complicated dependency chains - I don't know if we will - then we
can even document that.
> Depending on an external expat would be acceptable for me if the bits
> of GDB that depend on it would become optional, such that we can
> choose not to build them if expat is not available.
That's far more error-prone than either alternative. You complained
about the cost of testing the detection code, which I think is pretty
trivial; but this would require testing two different code paths in GDB
itself, and fielding "my flash doesn't work" bug reports from people
who failed to link against expat.
For scripting language support, I've been considering optional
dependencies, but for absolutely everything else I think we should
avoid them. Ship it, or require it at configure time, please.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-24 0:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 13:40 Daniel Jacobowitz
2006-07-18 13:57 ` Daniel Jacobowitz
2006-07-21 0:35 ` Joel Brobecker
2006-07-21 0:39 ` Daniel Jacobowitz
2006-07-21 0:45 ` Joel Brobecker
2006-07-23 21:52 ` Mark Kettenis
2006-07-23 22:03 ` Daniel Jacobowitz
2006-07-23 22:40 ` Christopher Faylor
2006-07-23 22:57 ` Daniel Jacobowitz
2006-07-23 23:13 ` Christopher Faylor
2006-07-24 0:17 ` Daniel Jacobowitz
2006-07-23 23:15 ` Pedro Alves
2006-07-23 23:18 ` Mark Kettenis
2006-07-24 0:15 ` Daniel Jacobowitz [this message]
2006-07-24 6:20 ` Joel Brobecker
2006-07-24 15:30 ` Christopher Faylor
2006-07-24 15:50 ` Daniel Jacobowitz
2006-07-24 16:37 ` Christopher Faylor
2006-07-24 21:58 ` Mark Kettenis
2006-07-24 19:50 ` Eli Zaretskii
2006-07-24 19:52 ` Daniel Jacobowitz
2006-07-24 20:29 ` Eli Zaretskii
2006-07-24 20:36 ` Daniel Jacobowitz
2006-07-24 15:24 ` Christopher Faylor
2006-07-24 19:47 ` Eli Zaretskii
2006-07-24 19:51 ` Daniel Jacobowitz
2006-07-24 20:22 ` Christopher Faylor
2006-07-24 20:29 ` Eli Zaretskii
2006-07-24 20:43 ` Daniel Jacobowitz
2006-07-24 21:42 ` Christopher Faylor
2006-07-24 22:18 ` DJ Delorie
2006-07-24 22:29 ` Mark Kettenis
2006-07-24 22:34 ` Daniel Jacobowitz
2006-07-24 22:37 ` Daniel Jacobowitz
2006-07-25 0:36 ` Christopher Faylor
2006-07-24 22:49 ` Mark Kettenis
2006-07-24 23:41 ` Daniel Jacobowitz
2006-07-25 0:47 ` Christopher Faylor
2006-07-31 17:33 ` Daniel Jacobowitz
2006-07-31 20:24 ` Daniel Jacobowitz
2006-07-31 20:39 ` Christopher Faylor
2006-07-31 21:33 ` Mark Kettenis
2006-08-01 0:42 ` Daniel Jacobowitz
2006-08-01 1:01 ` Daniel Jacobowitz
2006-07-24 22:08 ` Mark Kettenis
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=20060724001529.GA20102@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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