Javier, this beta builds for me on El Capitan. What exact steps did you
take to build Sage?
On Thursday, September 15, 2016 at 9:29:12 AM UTC-7, jhonrubia6 wrote:
>
> hardware is macbook air and OS version is OS 10.11.6
>
> El jueves, 15 de septiembre de 2016, 18:28:04 (UTC+2), jhonrubia6 escribi
So on another thread there was talk about whether we could
build sage with clang+gfortran on OS X.
Well it is not that bad and a little push in the right place would probably
get use 95% there.
I couldn’t build sagelib, I didn’t manage to get there. Here are the
packages that fail to build with cl
> Anyone remember when g95 was shipped as part of sage for OS X?
>>
>
> sure - in fact I even experimented with using R-supplied fortran instead,
> on a PPC OSX laptop :-)
>
>
>>
Oh boy does that take me back!
--
You received this message because you are subscribed to the Google Groups
hardware is macbook air and OS version is OS 10.11.6
El jueves, 15 de septiembre de 2016, 18:28:04 (UTC+2), jhonrubia6 escribió:
>
> Hi, I am getting an error building the beta4 (made a 'make distclean'
> before). Below the last lines of the log
>
> [sagelib-7.4.beta4] [ 1/269] Cythonizing sage/
Hi, I am getting an error building the beta4 (made a 'make distclean'
before). Below the last lines of the log
[sagelib-7.4.beta4] [ 1/269] Cythonizing sage/structure/misc.pyx
[sagelib-7.4.beta4]
[sagelib-7.4.beta4] Error compiling Cython file:
[sagelib-7.4.beta4]
--
Dear all,
The *Sage Days 79* are going to take place for the first time in Israel on
*November 21st to 24th 2016*
on the Givat Ram Campus of the Hebrew University of Jerusalem.
The aim of the meeting will be to introduce the software to students and
mathematicians in the region, with further
> There is an option --count to say how many ticket to tests before to stop.
> you may want to use that.
> You may even change it in your json config file during the patchbot run
> (not tested if this works to stop the bot)
Ok. I will try that. Thanks.
But Ctrl-C should not be very problemat
There is an option --count to say how many ticket to tests before to stop.
you may want to use that.
You may even change it in your json config file during the patchbot run
(not tested if this works to stop the bot)
But Ctrl-C should not be very problematic. Could you tell what kind of
problem
Dear all,
A patchbot is supposed to run forever, but realistically I should stop it
from time to time. Pushing ctrl-c stops the patchbot abruptly, and the
subsequent run seems sometimes to show somewhat erroneous behavior, perhaps
due to the spurious state of the files.
Is there a way to stop
