Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: Move gdbsupport to the top level
Date: Tue, 17 Sep 2019 16:45:00 -0000	[thread overview]
Message-ID: <83sgouvpmb.fsf@gnu.org> (raw)
In-Reply-To: <87tv9ayj7z.fsf@tromey.com> (message from Tom Tromey on Tue, 17	Sep 2019 10:34:56 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>,  palves@redhat.com,  gdb-patches@sourceware.org
> Date: Tue, 17 Sep 2019 10:34:56 -0600
> 
> >> That is, the plan is to remove the readline sources from the tree,
> >> and remove --with-system-readline, but follow the approach of some
> >> other libraries where one can unpack readline into the source tree
> >> and top-level configure will arrange to build it.
> 
> Eli> Would it be possible for whoever tars the release to drop the readline
> Eli> into the tree and build it under some opt-in configure-time switch?
> Eli> Making this opt-in might solve at least some of the problems that led
> Eli> to the decision, I think/hope.
> 
> Seems like a good suggestion to me.

Thanks, I hope it will be accepted.

My rationale is that, since GDB uses Readline in a much more
sophisticated way than many other packages, I'd expect GDB to depend
on a relatively recent version of Readline, where several important
changes were made lately, in particular those submitted by us.  Having
such a version ready in the tarball would, on the one side, allow
people not to upgrade their system Readline just to be able to build
and use GDB, and OTOH, will greatly simplify the task of finding that
specific version which GDB requires if they want to build GDB with a
version of Readline different from their installed one.


      reply	other threads:[~2019-09-17 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 21:03 Tom Tromey
2019-07-12  7:18 ` Andrew Pinski
2019-07-12 13:05   ` Tom Tromey
2019-07-15 20:10 ` Tom Tromey
2019-08-20 19:38 ` Pedro Alves
2019-08-20 20:22   ` Tom Tromey
2019-09-17 16:11     ` Tom Tromey
2019-09-17 16:16       ` Eli Zaretskii
2019-09-17 16:35         ` Tom Tromey
2019-09-17 16:45           ` Eli Zaretskii [this message]

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=83sgouvpmb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tom@tromey.com \
    /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