From: Eli Zaretskii <eliz@gnu.org>
To: Vibhav Pant <vibhavp@gmail.com>
Cc: emacs-devel@gnu.org, casouri@gmail.com
Subject: Re: HEAD fails to build with --enable-checking=structs
Date: Wed, 23 Nov 2022 18:52:13 +0200 [thread overview]
Message-ID: <83zgchy5oi.fsf@gnu.org> (raw)
In-Reply-To: <1125b2504a1ac9eccf44352a96837b3d96556a6b.camel@gmail.com> (message from Vibhav Pant on Wed, 23 Nov 2022 22:09:56 +0530)
> From: Vibhav Pant <vibhavp@gmail.com>
> Date: Wed, 23 Nov 2022 22:09:56 +0530
>
> HEAD fails to build when configured with "--enable-checking=structs"
> with the following error:
>
> pdumper.c: In function ‘dump_buffer’:
> pdumper.c:2752:3: error: #error "buffer changed. See CHECK_STRUCTS
> comment in config.h."
> 2752 | # error "buffer changed. See CHECK_STRUCTS comment in
> config.h."
> | ^~~~~
> pdumper.c: In function ‘dump_vectorlike’:
> pdumper.c:3004:3: error: #error "pvec_type changed. See
> CHECK_STRUCTS comment in config.h."
> 3004 | # error "pvec_type changed. See CHECK_STRUCTS comment in
> config.h."
> | ^~~~~
>
> IIUC, this might be due to the tree-sitter changes causing the dmpstruct
> hash for the respective types to change. pdumper.c should likely be
> updated with the new hashes and placeholder code to abort/error out if a
> buffer has associated tree-sitter parsers.
Did you read that comment to which this error message alludes? It tells how
to fix that, and the key to that is a file that is already there on your
system. So if you could post the relevant parts of it, that would help us
fix this faster.
TIA
next prev parent reply other threads:[~2022-11-23 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 16:39 HEAD fails to build with --enable-checking=structs Vibhav Pant
2022-11-23 16:52 ` Eli Zaretskii [this message]
2022-11-23 18:23 ` 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=83zgchy5oi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=vibhavp@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.