From: Tom Tromey <tom@tromey.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: static linking of gdb
Date: Mon, 06 Apr 2020 08:11:16 -0600 [thread overview]
Message-ID: <87y2r8embf.fsf@tromey.com> (raw)
In-Reply-To: <AM6PR03MB5170DE3A69633C7CC1ED728EE4C20@AM6PR03MB5170.eurprd03.prod.outlook.com> (Bernd Edlinger's message of "Mon, 6 Apr 2020 15:45:23 +0200")
>>>>> "Bernd" == Bernd Edlinger <bernd.edlinger@hotmail.de> writes:
Bernd> You definitely should, it is never too late to correct a wrong decision.
Bernd> Not being able to link gdb statically is a major usability-regression.
Here:
https://sourceware.org/pipermail/gdb-patches/2020-April/167390.html
... you said you don't want or need source highlight, so I suppose I
considered the matter closed.
Anyway, I don't really understand how your proposal would work.
How does it not just move the problem from gdb to this shim library?
It would be fine to patch source highlight to change the API.
I'm a maintainer of it, I'd approve clean patches to that end.
(However, I don't plan to do it myself, I only became a maintainer to
land a few fixes and do a release.)
Tom
prev parent reply other threads:[~2020-04-06 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 10:13 Bernd Edlinger
2020-04-05 13:17 ` Eli Zaretskii
2020-04-05 13:23 ` Bernd Edlinger
2020-04-05 13:48 ` Bernd Edlinger
2020-04-05 14:19 ` Eli Zaretskii
2020-04-05 14:56 ` Bernd Edlinger
2020-04-06 3:27 ` Bernd Edlinger
2020-04-06 7:14 ` Bernd Edlinger
2020-04-06 13:43 ` Tom Tromey
2020-04-06 13:42 ` Tom Tromey
2020-04-06 13:45 ` Bernd Edlinger
2020-04-06 14:11 ` Tom Tromey [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=87y2r8embf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=bernd.edlinger@hotmail.de \
--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