From: Andreas Enge <andreas@enge.fr>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/3] gnu: libtorrent: Update to 0.13.6.
Date: Sat, 3 Oct 2015 22:24:35 +0200 [thread overview]
Message-ID: <20151003202435.GA20014@debian> (raw)
In-Reply-To: <87k2r3afzy.fsf@gmail.com>
On Sat, Oct 03, 2015 at 10:50:25PM +0300, Alex Kost wrote:
> I had a problem with this one: it was built successfully but when I
> enabled tests, "make check" phase ate all my CPU and memory and after
> several minutes of messing with my HDD, I got:
There was no problem for me (with 8GB of RAM, of which I do not know how
much was used). So from my point of view, you could push these patches.
Andreas
next prev parent reply other threads:[~2015-10-03 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 19:50 [PATCH 2/3] gnu: libtorrent: Update to 0.13.6 Alex Kost
2015-10-03 20:24 ` Andreas Enge [this message]
2015-10-04 11:29 ` Alex Kost
2015-10-04 16:58 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151003202435.GA20014@debian \
--to=andreas@enge.fr \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).