From: "François Bissey" <frp.bissey@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] Cannot install sage-doc: insufficient memory
Date: Tue, 23 Sep 2014 20:51:13 +1200 [thread overview]
Message-ID: <F8631F0C-3637-4ADF-963C-CD7F58D7547F@gmail.com> (raw)
In-Reply-To: <20140923105116.b20c15c11713dfde9053c578@ukr.net>
According to upstream it all should be enough (there was a thread not so long ago
on sage-devel I am sure).
We must be doing something slightly differently. In any case, while it is nice
to have it building most people probably prefer the binary version. We only
started to use it for normal release because that official binaries for the doc
was so late we couldn’t release stable ebuilds for sage 6.2.
I will see what we could do.
François
On 23/09/2014, at 19:51, v_2e@ukr.net wrote:
> Hello!
>
> On Mon, 22 Sep 2014 09:52:41 +1200
> François Bissey <frp.bissey@gmail.com> wrote:
>
>> Hi Vladimir,
>>
>> Can you tell me: How many threads you are using (-j??)
>> and whether you have swap enabled on that machine.
>>
> I usually use a single thread in make.conf (-j1). I also have a 1 GB of
> swap space enabled.
>
> Vladimir
>
> -----
> <v_2e@ukr.net>
>
next prev parent reply other threads:[~2014-09-23 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 9:56 [gentoo-science] [sage-on-gentoo] Cannot install sage-doc: insufficient memory v_2e
2014-09-20 9:57 ` François Bissey
2014-09-20 10:02 ` v_2e
2014-09-20 10:01 ` François Bissey
2014-09-20 21:55 ` v_2e
2014-09-21 21:52 ` François Bissey
2014-09-23 7:51 ` v_2e
2014-09-23 8:51 ` François Bissey [this message]
2014-09-23 9:48 ` v_2e
2014-09-23 9:49 ` François Bissey
2014-09-23 11:35 ` v_2e
2014-09-23 11:38 ` François Bissey
2014-11-19 22:00 ` François Bissey
2014-09-25 0:59 ` François Bissey
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=F8631F0C-3637-4ADF-963C-CD7F58D7547F@gmail.com \
--to=frp.bissey@gmail.com \
--cc=gentoo-science@lists.gentoo.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