unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36225@debbugs.gnu.org
Subject: bug#36225: 26.2.90; Can't build master
Date: Sat, 15 Jun 2019 18:57:34 +0200	[thread overview]
Message-ID: <CAArVCkSJ-JczkcKcfQj2Tf+Ev07Lp=nMnvvVDCY3AL=W5_tOtw@mail.gmail.com> (raw)
In-Reply-To: <83sgsavll2.fsf@gnu.org>

Am Sa., 15. Juni 2019 um 18:51 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Sat, 15 Jun 2019 18:34:32 +0200
> > Cc: 36225@debbugs.gnu.org
> >
> > > The comment to CHECK_STRUCTS in src/config.h tells you what to do in
> > > this case.
> >
> > Yes, it says "If you change one of these structures, check that the
> > pdumper.c code is still valid", but since I didn't change the
> > structure, I can't decide whether the pdumper code is still valid.
> > Whoever changed the definition of Lisp_Buffer_Objfwd should make that
> > call.
>
> It says to update the pertinent hash in pdumper.c by manually copying
> the hash from dmpstruct.h.  The hash to be updated is called out by
> the error message.  So I think the information you need is there to
> fix your build.

That is not what I mean. Of course that fixes the build, that's not
the problem. But it would be incorrect and unsafe to blindly copy the
hash without investigating whether there were any changes to
Lisp_Buffer_Objfwd that would need to be reflected in pdumper.c.
That's the whole point of the hash check: force people to adapt
pdumper.c upon any struct change. That is what "If you change one of
these structures, check that the pdumper.c code is still valid" means:
whoever changed Lisp_Buffer_Objfwd (i.e., *not* me) needs to update
pdumper.c.





  reply	other threads:[~2019-06-15 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 15:39 bug#36225: 26.2.90; Can't build master Philipp
2019-06-15 16:03 ` Lars Ingebrigtsen
2019-06-15 16:31   ` Philipp Stephani
2019-06-15 16:22 ` Eli Zaretskii
2019-06-15 16:34   ` Philipp Stephani
2019-06-15 16:51     ` Eli Zaretskii
2019-06-15 16:57       ` Philipp Stephani [this message]
2019-06-15 17:20         ` 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

  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='CAArVCkSJ-JczkcKcfQj2Tf+Ev07Lp=nMnvvVDCY3AL=W5_tOtw@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=36225@debbugs.gnu.org \
    --cc=eliz@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).