Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix sagenb build #27257

Closed
jdemeyer opened this issue Feb 11, 2019 · 11 comments
Closed

Fix sagenb build #27257

jdemeyer opened this issue Feb 11, 2019 · 11 comments

Comments

@jdemeyer
Copy link

CC: @Konrad127123 @zimmermann6

Component: packages: standard

Branch/Commit: u/jdemeyer/fix_sagenb_build @ 3e48fd4

Issue created by migration from https://trac.sagemath.org/ticket/27257

@jdemeyer
Copy link
Author

Branch: u/jdemeyer/fix_sagenb_build

@Konrad127123
Copy link

Commit: 3e48fd4

@Konrad127123
Copy link

New commits:

3e48fd4Get rid of all "except ImportError" for sage

@jdemeyer
Copy link
Author

comment:3

Can you please try to reproduce the problem from #26686 with this branch?

@zimmermann6
Copy link

comment:4

Replying to @jdemeyer:

Can you please try to reproduce the problem from #26686 with this branch?

sorry I cannot. I only build Sage releases on my laptop (this takes ages and I have to make sure it does not heat too much).

@zimmermann6
Copy link

comment:5

after trying comment 18 in #26686, I can build Sage with make sagenb, but make -j1 still does not want to build the documentation:

$ make -j1
...
[dochtml] [tutorial ] Merging js index files...
[dochtml] [tutorial ] ... done (2115 js index entries)
[dochtml] [tutorial ] The HTML pages are in local/share/doc/sage/html/de/tutorial.
[dochtml] Error building the documentation.
[dochtml] Traceback (most recent call last):
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main
[dochtml]     "__main__", fname, loader, pkg_name)
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/runpy.py", line 72, in _run_code
[dochtml]     exec code in run_globals
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/site-packages/sage_setup/docbuild/__main__.py", line 2, in <module>
[dochtml]     main()
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py", line 1715, in main
[dochtml]     builder()
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py", line 342, in _wrapper
[dochtml]     build_many(build_other_doc, L)
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py", line 283, in build_many
[dochtml]     ret = x.get(99999)
[dochtml]   File "/usr/local/sage-8.6/local/lib/python2.7/multiprocessing/pool.py", line 572, in get
[dochtml]     raise self._value
[dochtml] OSError: WARNING: search index couldn't be loaded, but not all documents will be built: the index will be incomplete.
[dochtml] 
[dochtml]     Note: incremental documentation builds sometimes cause spurious
[dochtml]     error messages. To be certain that these are real errors, run
[dochtml]     "make doc-clean" first and try again.
Makefile:1993: recipe for target 'doc-html' failed
make[3]: *** [doc-html] Error 1
make[3]: Leaving directory '/usr/local/sage-8.6/build/make'
Makefile:1803: recipe for target 'all-start' failed
make[2]: *** [all-start] Error 2
make[2]: Leaving directory '/usr/local/sage-8.6/build/make'

@jdemeyer
Copy link
Author

comment:6

Does make doc-clean fix that latter error?

@zimmermann6
Copy link

comment:7

Replying to @jdemeyer:

Does make doc-clean fix that latter error?

yes it does. Thank you. But it was the first time since years that building Sage from source does not work.

@jdemeyer
Copy link
Author

comment:8

So is there anybody that can actually reproduce the problem from #26686? If not, this should be closed as "worksforme".

@zimmermann6
Copy link

comment:9

Replying to @jdemeyer:

So is there anybody that can actually reproduce the problem from #26686? If not, this should be closed as "worksforme".

I will try to rebuild Sage 8.6 from scratch, to see if the problem is reproducible.

By the way, while creating this ticket, you should have copied the description of the problem I had, since the description of this ticket is not very informative...

@zimmermann6
Copy link

comment:10

I tried again building Sage 8.6 from scratch and it worked fine. Since I'm unable to reproduce the problem, we can close that ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants