From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Move gdbsupport to the top level
Date: Tue, 17 Sep 2019 16:11:00 -0000 [thread overview]
Message-ID: <8736guzyv8.fsf@tromey.com> (raw)
In-Reply-To: <87r25fmvs2.fsf@tromey.com> (Tom Tromey's message of "Tue, 20 Aug 2019 14:22:53 -0600")
Tom> That message neglected option 4, which is removing readline from the
Tom> tree. (But making it continue to work if the sources are dropped in, as
Tom> we already do for libiconv etc.)
We discussed this at Cauldron and agreed to try this approach. 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.
Tom
next prev parent reply other threads:[~2019-09-17 16:11 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 [this message]
2019-09-17 16:16 ` Eli Zaretskii
2019-09-17 16:35 ` Tom Tromey
2019-09-17 16:45 ` Eli Zaretskii
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=8736guzyv8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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