From: Eli Zaretskii <eliz@gnu.org>
To: "Fāng-ruì Sòng" <maskray@google.com>
Cc: 43195-done@debbugs.gnu.org
Subject: bug#43195: [PATCH] Remove definitions of UP, BC and PC which should be provided by terminfo
Date: Sat, 12 Sep 2020 10:49:05 +0300 [thread overview]
Message-ID: <83k0wze8pa.fsf@gnu.org> (raw)
In-Reply-To: <CAFP8O3Jtvhn7HCOZrd+TQnHTBFkYCGg-XaQ6wjs_e8=DwjzOYA@mail.gmail.com> (message from Fāng-ruì Sòng on Sat, 12 Sep 2020 00:33:27 -0700)
> From: Fāng-ruì Sòng <maskray@google.com>
> Date: Sat, 12 Sep 2020 00:33:27 -0700
> Cc: 43195@debbugs.gnu.org
>
> > > I don't know whether it is worth mentioning that -fcommon/-fno-common does not
> > > cause a linker error when libtinfo.so is linked (a common/regular definition
> > > preempts a shared definition).
> > >
> > > -fno-common + libtinfo.a => multiple definition error
> >
> > OK, but the change works even in these other cases, right?
>
> Yep! The new code should work in other cases, -fcommon/-fno-common x
> libtinfo.a/libtinfo.so
OK, so I'm closing the bug report.
Thanks.
prev parent reply other threads:[~2020-09-12 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 0:57 bug#43195: [PATCH] Remove definitions of UP, BC and PC which should be provided by terminfo Fangrui Song via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-04 7:36 ` Eli Zaretskii
2020-09-04 15:38 ` Fangrui Song via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-12 7:19 ` Eli Zaretskii
2020-09-12 7:33 ` Unknown
2020-09-12 7:49 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k0wze8pa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43195-done@debbugs.gnu.org \
--cc=maskray@google.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).