Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add expat to the GDB sources
Date: Mon, 31 Jul 2006 21:33:00 -0000	[thread overview]
Message-ID: <200607312132.k6VLWpMT002274@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060731202422.GA16346@nevyn.them.org> (message from Daniel 	Jacobowitz on Mon, 31 Jul 2006 16:24:22 -0400)

> Date: Mon, 31 Jul 2006 16:24:22 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Mon, Jul 31, 2006 at 01:33:12PM -0400, Daniel Jacobowitz wrote:
> > As for optional versus required, I don't think there's a relevant FSF
> > position.  However, I very much wanted to use the XML target
> > descriptions in some cases to replace the C-coded ones.  So obviously
> > I prefer to require expat.
> 
> Which yields this patch.
> 
> If our final decision is to make all features which require expat
> optional, I can rework this patch to only issue a warning message,
> and update the documentation accordingly.  It currently:
>   - Searches $prefix/lib and $prefix/include for expat, as well
>     as the standard system directories.
>   - Offers a documented option to find expat elsewhere.
>   - Defines HAVE_LIBEXPAT in config.h.
> 
> I think I've said everything useful that I can say on this subject;
> I am not sure how to proceed.  The options that I see are:
> 
>   1. Refuse to use external libraries.
>   2. Make external libraries optional.
>   3. Require external libraries, with moderation and documentation.
> 
> Obviously I prefer 3, followed by 2.
> 
> Your thoughts welcome!

It all depends on what the external library is used for.  Making
readline optional wouldn't make much sense, since it is used for GDB's
primary user interface.  Making expat optional make much more sense to
me, as I can't see why I'd need it for a native debugger.

There's another reason why I'd like to see expat as an optional
library.  Currently we (OpenBSD) ship GDB in our base system.  This
would mean we'd have to include expat in our base system too;
something we'd rather not do especially if it doesn't give us any
benefits.  NetBSD and FreeBSD are in a similar situation I guess.

That said, I'm willing to give in under two conditions:

1. We add the necessary glue to the toplevel configure such that it
   accepts a --with-expat-dir option similar to the --with-gmp-dir
   option that's already there for GCC.  This will make it possible to
   keep building everything in one tree, which would come close to
   removing the objections I raised earlier about problemms installing
   expat on systems I use to test GDB on.

2. Try to keep the bits that need expat "optional", and review whether
   the code that needs it really benefits all of us, or only a few.

Mark


  parent reply	other threads:[~2006-07-31 21:33 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
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 [this message]
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=200607312132.k6VLWpMT002274@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=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