unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 40614-done@debbugs.gnu.org
Subject: bug#40614: 28.0.50; [feature/native-comp] straight.el fails to inject :straight keyword handler into use-package when use-package is native-compiled
Date: Mon, 20 Apr 2020 15:47:05 +0800	[thread overview]
Message-ID: <87zhb6vbt2.fsf@localhost> (raw)
In-Reply-To: <xjfv9lvv06s.fsf@sdf.org>

> I mean you can compile at speed 0, it requires a fraction of the memory
> required at speed 2.  You can even used that only to complete the
> compilation that failed.  In .gitlab-ci.yml we have examples on how to
> the speed can be controlled while building.

Thanks! I did not know that speed 0 would use less memory. Finally
managed to finish the compilation.

Best,
Ihor

Andrea Corallo <akrl@sdf.org> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>
>>
>> Sure. Though I plan to move the native-compile branch to my system
>> installation. Deferred compilation of built-in packages will not be easy
>> there, unless I run Emacs as root.
>>
>> Speed is actually not so big issue (at least to compile the built-in
>> elisp). The problem was that I tried to run make -j3 -> make -j2 -> make
>> -j1 hoping that less native-compilation processes would use less
>> memory. Everything, including make -j1 failed eventually and took a long
>> time because of using swap. Not sure what I can do for reducing memory
>> usage.
>
> I mean you can compile at speed 0, it requires a fraction of the memory
> required at speed 2.  You can even used that only to complete the
> compilation that failed.  In .gitlab-ci.yml we have examples on how to
> the speed can be controlled while building.
>
> -- 
> akrl@sdf.org

-- 
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg





      reply	other threads:[~2020-04-20  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  0:19 bug#40614: 28.0.50; [feature/native-comp] straight.el fails to inject :straight keyword handler into use-package when use-package is native-compiled Ihor Radchenko
2020-04-14 17:58 ` Andrea Corallo
2020-04-15  7:11   ` Ihor Radchenko
2020-04-15 22:21     ` Andrea Corallo
2020-04-19  9:42       ` Ihor Radchenko
2020-04-19 11:47         ` Andrea Corallo
2020-04-19 15:51           ` Ihor Radchenko
2020-04-19 17:45             ` Andrea Corallo
2020-04-20  7:47               ` Ihor Radchenko [this message]

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=87zhb6vbt2.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=40614-done@debbugs.gnu.org \
    --cc=akrl@sdf.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).