From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build
Date: Wed, 18 Oct 2017 15:50:07 +0100 [thread overview]
Message-ID: <1508338207.19915.79.camel@ipfire.org> (raw)
In-Reply-To: <491c7237-3a4f-ed01-70ac-f686f4e325fb@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi,
I have no idea why that is. It is supposed to use only 370MB for the
compression.
However, the build failed on the nightly build server, too which also has 8GB.
If xz uses that per core (of which this one has 8) this should still be well
under the limit.
I reverted the commits and now it will only compress in parallel. Please pull
from next.
-Michael
On Wed, 2017-10-18 at 16:22 +0200, Matthias Fischer wrote:
> On 18.10.2017 15:56, Matthias Fischer wrote:
> > On 18.10.2017 04:39, Michael Tremer wrote:
> > > Hi,
> > >
> > > how much memory does your build system have?
> > > ...
>
> Another info:
>
> ***SNIP***
> root(a)Devel: /home/matz/ipfire-2.x # xz --info-memory
> Total amount of physical memory (RAM): 7,787 MiB (8,165,240,832 B)
> Memory usage limit for compression: Disabled
> Memory usage limit for decompression: Disabled
> ***SNAP***
>
> 8GB. So why is it telling me 'out of memory...?
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-18 14:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 2:39 Matthias Fischer
2017-10-18 2:39 ` Michael Tremer
2017-10-18 13:56 ` Matthias Fischer
2017-10-18 14:22 ` Matthias Fischer
2017-10-18 14:50 ` Michael Tremer [this message]
2017-10-18 15:54 ` Matthias Fischer
2017-10-18 17:03 ` Matthias Fischer
2017-10-18 17:42 ` Michael Tremer
2017-10-19 14:00 ` Matthias Fischer
2017-10-19 19:10 ` Matthias Fischer
2017-10-23 14:22 ` Michael Tremer
2018-04-29 11:53 Matthias Fischer
2018-04-29 12:08 ` Peter Müller
2018-12-23 9:59 Matthias Fischer
2018-12-25 8:22 ` Michael Tremer
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer
2019-06-08 10:33 ` Matthias Fischer
2019-06-08 10:35 ` Michael Tremer
2019-06-08 11:38 ` Matthias Fischer
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=1508338207.19915.79.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox