From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: msys2 building issue
Date: Thu, 29 Mar 2018 15:22:28 +0300 [thread overview]
Message-ID: <83zi2rcbqz.fsf@gnu.org> (raw)
In-Reply-To: <87a7utgqql.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Tue, 27 Mar 2018 22:20:34 +0100
>
> x86_64
> no-deps zip 17min
> Deps-zip 3min
> installer 25min
>
> i686
> no deps zip 31min
> deps zip 47min
> installer 61min
>
> So, the installer is really slow to build (probably because of the
> compression I guess). But the second i686 step is really slow,
> especially the building the zips and installer.
Does this happen only when building both the 64-bit and the 32-bit
zips? What if you build only the 32-bit one -- do you get the same
slow times?
My next suspect is the way MSYS2 lets you build 32-bit binaries. I
know nothing about that, all I see is that you set 2 environment
variables, but could that cause Bash or Make or some other component
to run out of memory due to a bug or a memory leak?
> I don't think this is the Emacs build per se; it looks to me like a
> memory leak; the build process just gets slower and slower. In fact,
> I've had to reduce the parallalism of make or the whole process crashes
> with a resource allocation error.
Which program reports the error?
> But Process Manager reports that the VM has memory left.
What does Task Manager say about memory consumption of the various
programs involved in the build, like Bash, Make, and Python? Do you
see their memory growing to values that are unreasonably large?
The slow-down could be caused by memory consumption, so it's possible
the actual problem is with memory, not with slow builds.
next prev parent reply other threads:[~2018-03-29 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 21:20 msys2 building issue Phillip Lord
2018-03-29 12:22 ` Eli Zaretskii [this message]
2018-04-10 12:00 ` Phillip Lord
2018-04-10 15:17 ` Eli Zaretskii
[not found] ` <873702sxly.fsf@russet.org.uk>
[not found] ` <83muya3n6s.fsf@gnu.org>
2018-04-10 20:51 ` Phillip Lord
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=83zi2rcbqz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.