On 2013-01-17 20:48, Martin Albrecht wrote:
> Any other options?
Just live with it.
It still takes way more RAM to build the documentation than to build M4RIE.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to s
On 2013-01-17 20:48, Martin Albrecht wrote:
> = Split up the file =
>
> This can easily be done, its functions all handle different cases and do not
> interact. Volker suggested it might not make much of a difference because GCC
> optimises beyond file boundaries but if we actually produce diffe
Hi,
so it seems a lot of stories of people trying to build Sage on constrained
devices include something like: "the most time was spent building libm4rie all
of which pretty much is waiting for swap".
So let's take a harder look at M4RIE. The file in questions is - as far as I
can tell - conv
