From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build
Date: Wed, 18 Oct 2017 17:54:58 +0200 [thread overview]
Message-ID: <687f739f-8362-b703-e64b-3fbb7ab5b9fb@ipfire.org> (raw)
In-Reply-To: <1508338207.19915.79.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hi,
On 18.10.2017 16:50, Michael Tremer wrote:
> I reverted the commits and now it will only compress in parallel. Please pull
> from next.
***SNIP***
***Build is finished now and took 0 hour(s) 28 minute(s) 17 second(s)!
root(a)Devel: /home/matz/ipfire-2.x #
***SNAP***
It worked.
I'll try a complete clean build with '--memory=70%" and will report.
Best,
Matthias
P.S.:
...
The limit can be specified as a percentage of physical RAM.
Example: --memory=70%
...
next prev parent reply other threads:[~2017-10-18 15:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 2:39 Matthias Fischer
2017-10-18 2:39 ` Michael Tremer
2017-10-18 13:56 ` Matthias Fischer
2017-10-18 14:22 ` Matthias Fischer
2017-10-18 14:50 ` Michael Tremer
2017-10-18 15:54 ` Matthias Fischer [this message]
2017-10-18 17:03 ` Matthias Fischer
2017-10-18 17:42 ` Michael Tremer
2017-10-19 14:00 ` Matthias Fischer
2017-10-19 19:10 ` Matthias Fischer
2017-10-23 14:22 ` Michael Tremer
2018-04-29 11:53 Matthias Fischer
2018-04-29 12:08 ` Peter Müller
2018-12-23 9:59 Matthias Fischer
2018-12-25 8:22 ` Michael Tremer
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer
2019-06-08 10:33 ` Matthias Fischer
2019-06-08 10:35 ` Michael Tremer
2019-06-08 11:38 ` Matthias Fischer
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=687f739f-8362-b703-e64b-3fbb7ab5b9fb@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