From: Paul Eggert <eggert@cs.ucla.edu>
To: Philipp <p.stephani2@gmail.com>
Cc: 36929@debbugs.gnu.org
Subject: bug#36929: 27.0.50; Build on master broken
Date: Mon, 5 Aug 2019 16:36:24 -0700 [thread overview]
Message-ID: <af7ae018-1ccf-6d49-3391-2f07b617ce54@cs.ucla.edu> (raw)
In-Reply-To: <m2h86wxbnr.fsf@gmail.com>
> Should we maybe define CHECK_STRUCTS unconditionally to prevent issues
> like this?
Let's not, because CHECK_STRUCTS is more trouble than it's worth when doing
serious development. See commit 9994bf17cf532f2e1d4310341da7180342202191 and
related discussion.
If you run into this problem again, feel free to do what Eli did and commit a
change to the hash to get your --enable-checking=structs build to work again. I
don't bother because --enable-checking=structs is a waste of time for me, and I
recommend against it.
next prev parent reply other threads:[~2019-08-05 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 8:24 bug#36929: 27.0.50; Build on master broken Philipp
2019-08-05 16:12 ` Mattias Engdegård
2019-08-05 17:05 ` Philipp Stephani
2019-08-05 17:08 ` Mattias Engdegård
2019-08-05 16:16 ` Eli Zaretskii
2019-08-05 23:36 ` Paul Eggert [this message]
2019-08-06 12:26 ` Andy Moreton
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=af7ae018-1ccf-6d49-3391-2f07b617ce54@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=36929@debbugs.gnu.org \
--cc=p.stephani2@gmail.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).