From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build
Date: Wed, 18 Oct 2017 03:39:59 +0100 [thread overview]
Message-ID: <1508294399.2995.18.camel@ipfire.org> (raw)
In-Reply-To: <64131ab1-b34a-cbfa-024a-12d9ef2c4212@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Hi,
how much memory does your build system have?
I changed the compression algorithm and it will now use up to ~370MB of
memory (probably times the number of processor cores you have).
If that is too much, we need to change this to something lower again.
The benefit right now is, that the ISO image is about 15 MB smaller.
-Michael
On Wed, 2017-10-18 at 04:39 +0200, Matthias Fischer wrote:
> Hi,
>
> Current 'next' always gives me:
>
> ***SNIP***
> ...
> tar -c -C / --files-from=/tmp/ROOTFILES \
> -f /ipfire.tar --exclude='#*' --exclude='dev/pts/*' \
> --exclude='proc/*' --exclude='tmp/ROOTFILES'
> rm -f /tmp/ROOTFILES
> tar -x -C /tmp -f /ipfire.tar
> rm -f /ipfire.tar
> cd /tmp && tar cf /install/cdrom/distro.img --xz * && rm -rf *
> xz: (stdin): Cannot allocate memory
> make: *** [cdrom:75: /usr/src/log/cdrom] Error 141
> ...
> ***SNAP***
>
> Building on Ubuntu 16.04.3 LTS / 32bit.
>
> Can anyone confirm?
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-18 2:39 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 [this message]
2017-10-18 13:56 ` Matthias Fischer
2017-10-18 14:22 ` Matthias Fischer
2017-10-18 14:50 ` Michael Tremer
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=1508294399.2995.18.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