public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <06a7aa500aa06e9a3dbb692a1759fc76c7e650f9.camel@ipfire.org> (raw)
In-Reply-To: <a836716f-9556-c515-1a55-5cde7149c1d1@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

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

  reply	other threads:[~2018-05-22 18:03 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 [this message]
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

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=06a7aa500aa06e9a3dbb692a1759fc76c7e650f9.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