From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build => 'cannot allocate memory'
Date: Tue, 22 May 2018 19:03:00 +0100
Message-ID: <06a7aa500aa06e9a3dbb692a1759fc76c7e650f9.camel@ipfire.org>
In-Reply-To: <a836716f-9556-c515-1a55-5cde7149c1d1@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3160625062889140819=="
List-Id: <development.lists.ipfire.org>

--===============3160625062889140819==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I thought xz was now limited to lower memory. Could you add -v to see what xz
has decided to do?

-Michael

On Tue, 2018-05-22 at 18:31 +0200, Matthias Fischer wrote:
> Hi!
>=20
> Sorry, but last commit "make.sh: Use all processor cores for
> compression" causes the build to break.
>=20
> See
> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Dc8453e87599fe66f4=
d18d901bc
> 9dc431306afa2d
>=20
> Build stops with:
>=20
> ***SNIP***
> ...
> rm -f /tmp/ROOTFILES
> tar -x -C /tmp -f /ipfire.tar
> rm -f /ipfire.tar
> cd /tmp && tar cf - * | xz -T8 -8 --memory=3D5450MiB >
> /install/cdrom/distro.img && rm -rf *
> xz: (stdin): Cannot allocate memory
> make: *** [cdrom:66: /usr/src/log/cdrom] Error 1
> ...
> ***SNAP***
>=20
> On my machine, 'lsf/cdrom' doesn't like '-T8'. It needed '-T4'.
> I experienced this already during my tests.
>=20
> Can anyone confirm?
>=20
> Best,
> Matthias
>=20
> P.S.: Hardware is i7/2600 with HT, 8 GB RAM.

--===============3160625062889140819==--