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 [thread overview]
Message-ID: <07603464cacc995aceffcdc9be54523362dfded7.camel@ipfire.org> (raw)
In-Reply-To: <fb8aadcf-3a2d-1a6c-631f-29f672c9b9a1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Sat, 2018-05-26 at 18:39 +0200, Matthias Fischer wrote:
> Hi,
>
> On 25.05.2018 19:21, Matthias Fischer wrote:
> > I'll wait until the current building with 90% is finished and report.
>
> In short - results for last 'next'-build (32bit):
>
> ipfire-2.19.2gb-ext4.i586-full-core121.img.xz => 176 MB
> ipfire-2.19.i586-full-core121.iso => 207 MB
>
> From me: 32bit seems to be ok.
>
> 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
>
> Best,
> Matthias
prev parent reply other threads:[~2018-05-29 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 16:31 Matthias Fischer
2018-05-22 18:03 ` Michael Tremer
2018-05-22 19:05 ` Matthias Fischer
2018-05-22 19:57 ` Michael Tremer
2018-05-23 11:18 ` Michael Tremer
2018-05-24 16:54 ` Matthias Fischer
2018-05-25 13:13 ` Michael Tremer
2018-05-25 17:21 ` Matthias Fischer
2018-05-25 18:20 ` Matthias Fischer
2018-05-26 16:39 ` Matthias Fischer
2018-05-29 19:38 ` Michael Tremer [this message]
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=07603464cacc995aceffcdc9be54523362dfded7.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