From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build => 'cannot allocate memory'
Date: Sat, 26 May 2018 18:39:45 +0200 [thread overview]
Message-ID: <fb8aadcf-3a2d-1a6c-631f-29f672c9b9a1@ipfire.org> (raw)
In-Reply-To: <7346e4b7-0b24-0192-5ba9-5cf108704204@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
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... ;-)
Best,
Matthias
next prev parent reply other threads:[~2018-05-26 16:39 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 [this message]
2018-05-29 19:38 ` Michael Tremer
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=fb8aadcf-3a2d-1a6c-631f-29f672c9b9a1@ipfire.org \
--to=matthias.fischer@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