From: Marius Bakke <mbakke@fastmail.com>
To: Jeff Bauer <jbauer@rubic.com>, 35108@debbugs.gnu.org
Subject: bug#35108: ungoogled-chromium fails to install
Date: Thu, 16 May 2019 16:52:14 +0200 [thread overview]
Message-ID: <87ef4yo3j5.fsf@devup.no> (raw)
In-Reply-To: <20190516134839.GB2637@rubic.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Jeff Bauer <jbauer@rubic.com> writes:
>> Unfortunately, you cropped the interesting part of the error message.
>> Can you show us more? It would interesting to see what happened before.
>>
>> This backtrace just shows us that the command we invoke with “invoke”
>> returned an error. That’s not very helpful.
>>
>> --
>> Ricardo
>
> I'm not the OP, but I got the same error message while attempting
> to install ungoogled-chromium. Here's the last 100 lines of my
> log. I can submit the entire compressed file if it would be
> helpful.
Hello!
The problem with Ungoogled-Chromium is that it (at some point) uses
6-8GiB of memory *per core* during the build.
It would be great to codify this constraint in the package definition,
but I can't think of an easy way short of parsing /proc/meminfo.
For now we can disable parallel building, which will arguably provide
a better user experience than thrashing and crashing systems...
Thoughts?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-05-16 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 17:08 bug#35108: ungoogled-chromium fails to install Blackbeard
2019-04-02 20:09 ` Ricardo Wurmus
2019-05-16 13:48 ` Jeff Bauer
2019-05-16 14:52 ` Marius Bakke [this message]
2019-05-16 17:31 ` Jeff Bauer
2019-05-25 11:06 ` Marius Bakke
2020-04-07 19:27 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef4yo3j5.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=35108@debbugs.gnu.org \
--cc=jbauer@rubic.com \
/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/guix.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).