From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 43724@debbugs.gnu.org
Subject: bug#43724: build failure in dbusbind
Date: Wed, 30 Sep 2020 19:34:41 +0200 [thread overview]
Message-ID: <878scr183y.fsf@gnus.org> (raw)
In-Reply-To: <k7362zb7dv.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 30 Sep 2020 11:40:12 -0400")
Glenn Morris <rgm@gnu.org> writes:
> On CentOS 8.2 with gcc 8.3.1 at a190a446e with --enable-check-lisp-object-type:
Just a data point -- this also fails for me on Debian bullseye with
gcc version 10.2.0 (Debian 10.2.0-6)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-30 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 15:40 bug#43724: build failure in dbusbind Glenn Morris
2020-09-30 17:34 ` Lars Ingebrigtsen [this message]
2020-10-01 8:36 ` Michael Albinus
2020-10-01 8:45 ` Andreas Schwab
2020-10-01 9:22 ` Michael Albinus
2020-10-01 8:49 ` Robert Pluim
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=878scr183y.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43724@debbugs.gnu.org \
--cc=rgm@gnu.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.
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).