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, 29 May 2018 20:38:08 +0100
Message-ID: <07603464cacc995aceffcdc9be54523362dfded7.camel@ipfire.org>
In-Reply-To: <fb8aadcf-3a2d-1a6c-631f-29f672c9b9a1@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6655010486445280529=="
List-Id: <development.lists.ipfire.org>

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

On Sat, 2018-05-26 at 18:39 +0200, Matthias Fischer wrote:
> Hi,
>=20
> On 25.05.2018 19:21, Matthias Fischer wrote:
> > I'll wait until the current building with 90% is finished and report.
>=20
> In short - results for last 'next'-build (32bit):
>=20
> ipfire-2.19.2gb-ext4.i586-full-core121.img.xz =3D> 176 MB
> ipfire-2.19.i586-full-core121.iso =3D> 207 MB
>=20
> From me: 32bit seems to be ok.
>=20
> Still curious about results for 64bit... ;-)

The compressed output will be exactly the same. It won't compress any better.=
 It
will just use more memory and CPU cores and therefore will be faster.

It is running through on all build systems and even on the ARM machines.

Best,
-Michael

>=20
> Best,
> Matthias

--===============6655010486445280529==--