The ungoogled-chromium build process no longer requires boatloads of
memory, and is also much more stable on the build farm. Closing.
Jeff Bauer writes:
> On Thu, May 16, 2019 at 04:52:14PM +0200, Marius Bakke wrote:
>> 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 th
On Thu, May 16, 2019 at 04:52:14PM +0200, Marius Bakke wrote:
> 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
Jeff Bauer 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.
>>
>>
> 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 O
Blackbeard writes:
> Hello, I am having trouble to install ungoogled-chromium.
>
> I've tried several times and with different 'guix pull' commits, but it
> keeps failing at around 84%. This is from the logs:
>
>
> ninja: build stopped: subcommand failed.
> Backtrace:
>4 (primitive-
Hello, I am having trouble to install ungoogled-chromium.
I've tried several times and with different 'guix pull' commits, but it
keeps failing at around 84%. This is from the logs:
ninja: build stopped: subcommand failed.
Backtrace:
4 (primitive-load "/gnu/store/25402q0d5mdh4rkp155rh
