Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 20:43:00 -0000	[thread overview]
Message-ID: <20060724204310.GH15759@nevyn.them.org> (raw)
In-Reply-To: <uvepmeohm.fsf@gnu.org>

On Mon, Jul 24, 2006 at 11:28:53PM +0300, Eli Zaretskii wrote:
> They come with GCC and with Binutils.

Yes, that's true.  But they also come with instructions that their
development headers should not be installed, and by default 'make
install' does not install them - precisely because they're not meant to
be used this way.

> Also, you seem to be saying that, once we remove readline, say, one
> would have to use the last released version of readline for building
> GDB, while the build out of CVS will still use the CVS version, is
> that right?  If so, it's a bad idea, IMHO.

I apologize if I gave that impression!  Neither CVS nor released GDB
tarballs would go out and download readline for you; both would use the
same thing, i.e. what you have installed.

This can be a pain if you have tight version requirements on the
supported libraries; but we don't.  We've worked with the last several
years of releases of readline, for instance, basically without change.

> > In an ideal world, maybe there would be independent
> > releases, and we could use them.  But BFD in particular doesn't have a
> > stable API and (as recently discussed on the binutils list) doesn't
> > have an interest in one.
> > 
> > Compare to readline, tcl, and expat, each used by hundreds of different
> > programs.
> 
> Sorry, I don't see any significant difference.  The number of packages
> is not really relevant; what is relevant is how easier or harder would
> things become for Joe Random Hacker Who Just Wants To Build GDB.
> Perhaps Chris and Daniel don't see any problem because they have the
> latest versions of everything on their machines, at all times.  From
> my point of view, about the worst annoyance of Free Software is what
> happens when I "./configure; make" just to find out that I need two
> more packages, which in turn want each one two more packages, which
> want yet some more ...

This is what installation documentation is for!  We already have a
section in the manual that covers running configure.

I don't always have things installed.  I confess that I do use a modern
packaging system that makes installing dependencies relatively
painless, but I do it by hand from time to time too.

And neither readline nor expat has a substantial dependency chain.

I wouldn't suggest that we require an installation of GNOME, on the
other hand.

> In other words, when I download a package, I want it ideally to build
> out of the box, period.  No questions asked, and no additional
> prerequisites that could turn a simple build job into an agony that
> lasts the better part of my day, because each prerequisite package
> needs a bit of tweaking to build and install properly.  By contrast,
> when I get readline etc. with GDB, I can be _certain_ that someone
> already tried and succeeded to build _this_ version of the library
> with _this_ configury and _this_ GDB release.

FYI, what we are doing with readline is against the FSF's recently
clarified policy.  We're shipping a locally modified copy of a GNU
package.  This was the subject of one of the past few messages to
gnu-prog.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-07-24 20:43 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 [this message]
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=20060724204310.GH15759@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