Skip to content
This repository was archived by the owner on Feb 1, 2023. It is now read-only.

Commit 7683168

Browse files
author
Matthias Koeppe
committed
Improve troubleshooting instructions
1 parent 082e238 commit 7683168

File tree

2 files changed

+22
-14
lines changed

2 files changed

+22
-14
lines changed

README.md

Lines changed: 6 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -331,20 +331,12 @@ as well as the version-specific Sage Installation FAQ in the [Sage Release
331331
Tour](https://wiki.sagemath.org/ReleaseTours) corresponding to the
332332
version that you are installing.
333333

334-
Also note the following. Each separate component of Sage is
335-
contained in an spkg; these are stored in `build/pkgs/`. As each one
336-
is built, a build log is stored in `logs/pkgs/`, so you can browse these
337-
to find error messages. If an spkg fails to build, the whole build
338-
process will stop soon after, so check the most recent log files
339-
first, or run
340-
341-
grep -li "^Error" logs/pkgs/*
342-
343-
from the top-level Sage directory to find log files with error
344-
messages in them. Send (a small part of) the relevant log file to the
345-
[sage-devel mailing list](https://groups.google.com/group/sage-devel),
346-
making sure to include at least some of the error messages; probably
347-
someone there will have some helpful suggestions.
334+
Please do not hesitate to ask for help in the [SageMath forum
335+
](https://ask.sagemath.org/questions/) or the [sage-support mailing
336+
list](https://groups.google.com/forum/#!forum/sage-support). The
337+
[Troubleshooting section in the Sage Installation Guide]() provides
338+
instructions on what information to provide so that we can provide
339+
help more effectively.
348340

349341
Contributing to Sage
350342
--------------------

src/doc/en/installation/troubles.rst

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,3 +17,19 @@ therefore not covered by this manual.
1717
Also please do not hesitate to ask for help in the `SageMath forum
1818
<https://ask.sagemath.org/questions/>`_ or the `sage-support mailing
1919
list <https://groups.google.com/forum/#!forum/sage-support>`_.
20+
21+
Also note the following. Each separate component of Sage is
22+
contained in an SPKG; these are stored in `build/pkgs/`. As each one
23+
is built, a build log is stored in `logs/pkgs/`, so you can browse these
24+
to find error messages. If an SPKG fails to build, the whole build
25+
process will stop soon after, so check the most recent log files
26+
first, or run::
27+
28+
grep -li "^Error" logs/pkgs/*
29+
30+
from the top-level Sage directory to find log files with error
31+
messages in them. Send the file ``config.log`` as well as (a small
32+
part of) the relevant log file to the `sage-support mailing list
33+
<https://groups.google.com/group/sage-support>`_, making sure to
34+
include at least some of the error messages; probably someone there
35+
will have some helpful suggestions.

0 commit comments

Comments
 (0)