Building SageMath 6.8 from source on 32-bit Ubuntu 15.04

[Brenton]

Hi, 

I've been downloading the latest SageMath release source code via Git and when I did this for beta releases and 6.8.rc0, the build happened without error after I downloaded the singular patch into `build/pkgs/singular/patches/`. SageMath 6.8.rc1 & 6.8 are where the problem is. Running `make` from their directory gives the following error message:

Error building the documentation.


Note: incremental documentation builds sometimes cause spurious
error messages. To be certain that these are real errors, run
"make doc-clean" first and try again.
Traceback (most recent call last):
  File "/home/fusion809/sage/src/doc/common/builder.py", line 1626, in <module>
    getattr(get_builder(name), type)()
  File "/home/fusion809/sage/src/doc/common/builder.py", line 292, in _wrapper
    getattr(get_builder(document), 'inventory')(*args, **kwds)
  File "/home/fusion809/sage/src/doc/common/builder.py", line 503, in _wrapper
    x.get(99999)
  File "/home/fusion809/sage/local/lib/python/multiprocessing/pool.py", line 558, in get
    raise self._value
OSError: [misc     ] /home/fusion809/sage/src/doc/en/reference/misc/sage/misc/ascii_art.rst:11: WARNING: autodoc can't import/find module 'sage.misc.ascii_art', it reported error: "No module named ascii_art", please check your spelling and sys.path


Makefile:742: recipe for target 'doc-html' failed
make[2]: *** [doc-html] Error 1
make[2]: Leaving directory '/home/fusion809/sage/build/make'
Makefile:563: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/fusion809/sage/build/make'


real 16m54.732s
user 12m49.636s
sys 0m12.840s
***************************************************************
Error building Sage.


The following package(s) may have failed to build (not necessarily
during this run of 'make all'):


* documentation: dochtml
  log file: /home/fusion809/sage/logs/pkgs/../dochtml.log

Attached is my build file.

Thanks for your time,

Brenton

[John H Palmieri]

Did you try this:


Note: incremental documentation builds sometimes cause spurious
error messages. To be certain that these are real errors, run
"make doc-clean" first and try again.




  John