unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, dancol@dancol.org, emacs-devel@gnu.org
Subject: Re: pdumper bootstrap error
Date: Mon, 21 Jan 2019 21:20:58 +0000	[thread overview]
Message-ID: <20190121212058.GA66743@breton.holly.idiocy.org> (raw)
In-Reply-To: <83a7jtagz1.fsf@gnu.org>

On Mon, Jan 21, 2019 at 10:33:22PM +0200, Eli Zaretskii wrote:
> > Date: Mon, 21 Jan 2019 19:43:06 +0000
> > From: Alan Third <alan@idiocy.org>
> > Cc: eggert@cs.ucla.edu, dancol@dancol.org, emacs-devel@gnu.org
> > 
> > I can see the unexec code path replacing bootstrap-emacs, but the
> > pdumper code doesn’t.
> 
> That's expected: with unexec, the dumped Emacs executable is different
> from bootstrap-emacs, but with pdumper they are identical.  That
> comment is only correct for the unexec case.

I see.

> since we have just produced a new temacs, this rule is expected to
> fire, and produce a new bootstrap-emacs. But on your system, it
> doesn't. My first suspicion is that this has something to do with
> time granularity of the filesystem on which you run this: Make
> doesn't notice that temacs is newer than bootstrap-emacs, so it
> doesn't remake the latter. Is it possible that the time stamps of
> temacs and bootstrap-emacs are such that this happens? If so, what
> kind of filesystem is that?

I don’t think this is the issue. I’m using apfs, which a quick google
tells me has ‘nanosecond’ accuracy. Besides:

-rwxr-xr-x  1 alan  staff  7057932 21 Jan 19:37 bootstrap-emacs
-rwxr-xr-x  1 alan  staff  7057932 21 Jan 20:49 temacs

> > make[3]: Circular bootstrap-emacs <- temacs dependency dropped.
> 
> This warning is also worrisome: I don't get it, and I fail to see any
> such circular dependency in my Makefile.  Maybe it's because macuvs.h
> depends on bootstrap-emacs, and on macOS macuvs.h is indeed used?

This indeed looks like it’s probably the issue. I think I’ve had that
message for as long as I’ve been building Emacs. I just assumed it was
informational and not an actual error.

If I comment out this:

$(srcdir)/macuvs.h $(lispsource)/international/charprop.el: \
  bootstrap-emacs$(EXEEXT) $(bootstrap_pdmp) FORCE
	$(MAKE) -C ../admin/unidata all EMACS="../$(bootstrap_exe)"

the errors go away.
-- 
Alan Third



  reply	other threads:[~2019-01-21 21:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 22:25 pdumper bootstrap error Alan Third
2019-01-19 22:38 ` Philipp Stephani
2019-01-19 22:52 ` Paul Eggert
2019-01-20 10:57   ` Alan Third
2019-01-21 16:53     ` Alan Third
2019-01-21 17:18       ` Eli Zaretskii
2019-01-21 19:07         ` Eli Zaretskii
2019-01-21 19:50           ` Alan Third
2019-01-21 19:43         ` Alan Third
2019-01-21 20:33           ` Eli Zaretskii
2019-01-21 21:20             ` Alan Third [this message]
2019-01-22  3:31               ` Eli Zaretskii
2019-01-22 16:49                 ` Eli Zaretskii
2019-01-22 23:20                   ` Alan Third
2019-01-23 16:24                     ` Eli Zaretskii
2019-01-23 19:47                       ` Alan Third
2019-01-23 19:56                         ` Eli Zaretskii
2019-01-25 22:17                           ` Alan Third
2019-01-22 17:14                 ` Alan Third

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=20190121212058.GA66743@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=dancol@dancol.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).