From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17622 <17622@debbugs.gnu.org>, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: bug#17622: 24.4.50; bootstrap failure
Date: Thu, 29 May 2014 18:44:32 +0200 [thread overview]
Message-ID: <CAFgFV9P1BdHQAe4bH6++p=iQfxCB2UEto8tA14u8TzFJ7JUZqg@mail.gmail.com> (raw)
In-Reply-To: <83oayghb4n.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Ok, thanks for fixing it in the repo.
Fabrice
2014-05-29 17:12 GMT+02:00 Eli Zaretskii <eliz@gnu.org>:
> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Thu, 29 May 2014 16:24:12 +0200
> > Cc: Katsumi Yamaoka <yamaoka@jpl.org>, 17622 <17622@debbugs.gnu.org>,
> Eli Zaretskii <eliz@gnu.org>
> >
> > @@ -5282,6 +5277,10 @@
> > {
> > struct buffer *b;
> >
> > +#ifndef WINDOWSNT
> > + mmap_regions = NULL;
> > + mmap_fd = -1;
> > +#endif
> > /* We cannot dump buffers with meaningful addresses that can be
> > used by the dumped Emacs. We map new memory for them here. */
> > FOR_EACH_BUFFER (b)
>
> That's what I did, except that this (and the FOR_EACH_BUFFER loop
> after it) should only be done in the dumped emacs.
>
[-- Attachment #2: Type: text/html, Size: 1421 bytes --]
next prev parent reply other threads:[~2014-05-29 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 23:45 bug#17622: 24.4.50; bootstrap failure Katsumi Yamaoka
2014-05-29 2:02 ` Katsumi Yamaoka
2014-05-29 4:56 ` Katsumi Yamaoka
2014-05-29 12:38 ` Ken Brown
2014-05-29 12:55 ` Fabrice Popineau
2014-05-29 13:29 ` Ken Brown
2014-05-29 13:54 ` Fabrice Popineau
2014-05-29 14:17 ` Ken Brown
2014-05-29 14:24 ` Fabrice Popineau
2014-05-29 15:12 ` Eli Zaretskii
2014-05-29 16:44 ` Fabrice Popineau [this message]
2014-05-29 22:52 ` Katsumi Yamaoka
2014-05-29 15:09 ` Eli Zaretskii
2014-05-29 15:08 ` Eli Zaretskii
2014-05-29 14:59 ` 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='CAFgFV9P1BdHQAe4bH6++p=iQfxCB2UEto8tA14u8TzFJ7JUZqg@mail.gmail.com' \
--to=fabrice.popineau@gmail.com \
--cc=17622@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yamaoka@jpl.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 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.