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, 24 Jul 2006 22:49:00 -0000 [thread overview]
Message-ID: <200607242248.k6OMmp1X029286@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060724223413.GA20726@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 24 Jul 2006 18:34:13 -0400)
> Date: Mon, 24 Jul 2006 18:34:13 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Tue, Jul 25, 2006 at 12:29:28AM +0200, Mark Kettenis wrote:
> > > But, where does this philosophy end? Are you *really* advocating that
> > > every shipping package should include the source code of any libraries
> > > that they use? So gdb should also include ncurses?
> >
> > The philosophy has always been that one should be able to build a GNU
> > toolchain without any external dependencies, to be able to bootstrap
> > into a situation wher you can use the toolchain to build other Free
> > Software.
>
> When was the last time you tried to build GCC? Even just building it
> has pretty hefty requirements:
>
> http://gcc.gnu.org/install/prerequisites.html
>
> GMP/MPFR and zip fill the same sort of role that expat and readline
> would. The GNU Make version requirement also often needs to be
> manually met by users wanting to build GCC - lots of systems don't have
> an adequate Make for the GCC build system.
Where do you think my frstration about external dependencies comes
from ;-). However, GCC will build fine without most of those
packages: without GMP/MPFR you won't get gfortran, and without zip you
won't get gjc/libjava. But at least you can still build the C
compiler, which you can then use to build the other dependencies.
I think the GNU Make requirements are a serious mistake by the GCC
developers.
Translated to GDB this would mean that without expat you'd still get a
usable gdb, but loose goodies like the new flash support (which isn't
terribly useful for a native gdb anyway).
next prev parent reply other threads:[~2006-07-24 22:49 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 [this message]
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=200607242248.k6OMmp1X029286@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