I got an error building Sage due to a package failing to be built. I have a
Lenovo Thinkpad 11e running Ubuntu Mate 16.04 LTS. Before beginning the
build, I checked that I had all the dependencies and suggested packages
installed beforehand. Then I pulled the code in through git and ran `make`.
My attempt to build Sage 7.6 resulted in an error. Before beginning, I
checked that I had all the required dependencies and suggested programs.
Then I got the code through git, set MAKE='make -j5 -j4' since I have four
physical cpu cores, and ran make. Make ran for about 45 min. and then
return
On Thursday, July 13, 2017 at 12:17:43 AM UTC-7, HG wrote:
>
> Did you read this ... if it can help you ?
>
> https://groups.google.com/forum/#!topic/sage-devel/zQsZsivts0I
>
> Le 13/07/2017 à 02:54, Christopher Phoenix a écrit :
>
> My attempt to build Sage 7.6 resulted in an
loring
all the possibilities of Sage. Thanks for the help!
On Thursday, July 13, 2017 at 12:17:43 AM UTC-7, HG wrote:
>
> Did you read this ... if it can help you ?
>
> https://groups.google.com/forum/#!topic/sage-devel/zQsZsivts0I
>
> Le 13/07/2017 à 02:54, Christopher Phoenix a écrit :
I just ran ./sage --testall to test my new build of Sage like the
installation guide recommended. It took over six hours on my hardware
(Lenovo Thinkpad 11e, Intel Celeron N2940, 4 gb ram, 500 gb hdd). When the
tests finished, four doctests were listed as having timed out.
sage -t local/lib/pyt
ou might re-run these (timed out) tests separately. However, it's not
> uncommon to see these, in particular if you run tests in parallel on a
> loaded machine.
>
> On Friday, July 14, 2017 at 8:52:30 PM UTC+1, Christopher Phoenix wrote:
>>
>> I just ran ./sage --testall
> same terminal in which you are building sage.
>
> export OPENBLAS_CONFIGURE="TARGET=ATOM"
>
> This resolved the problem as reported in this other thread:
> https://groups.google.com/forum/#!topic/sage-devel/zQsZsivts0I
>
> Good luck!
>
>
> On Wednesday, July 12, 2
