#11959: Remove the necessity to set SAGE_PARALLEL_SPKG_BUILD
---------------------------+------------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-4.7.3
Component: build | Keywords: SAGE_PARALLEL_SPKG_BUILD MAKE -j
--jobs
Work_issues: | Upstream: N/A
Reviewer: | Author: John Palmieri
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by jhpalmieri):
Some comments about the new versions:
- I've added a "build-serial" target in the Makefile.
- spkg/install writes "parallel-make.cfg" in the directory "spkg", since
that seems to be the current directory when the makefile "standard/deps"
is executed.
- Leif's proposed change to spkg/install regarding moving "makefile" to
"Makefile" didn't seem to work on OS X, probably because of the stupid way
OS X deals with upper and lower case in their standard file system. Or
maybe I did something else wrong. Anyway, I didn't change that part of
the script.
- I haven't put everything possible into the top-level README file: the
installation guide is supposed to have all of the details. I did add a
comment about the spkg/logs/ files. See also #11926, which adds a message
about spkg/logs/PKG.log to the error message printed by sage-spkg.
- in the installation guide, I added a few comments about problems
building ATLAS.
By the way, is there anything wrong with this kind of change:
{{{
#!diff
diff --git a/spkg/install b/spkg/install
--- a/spkg/install
+++ b/spkg/install
@@ -483,19 +483,19 @@ fi
echo "Sage build/upgrade complete!"
if [ "$1" = "all" ]; then
- echo
- echo "To install small scripts to directly run Sage's versions of
GAP,"
- echo "the PARI/GP interpreter, Maxima, or Singular etc. (by typing
e.g."
- echo "just 'gap' or 'gp') into a standard 'bin' directory, start
Sage"
- echo "by typing 'sage' (or './sage') and enter something like"
- echo
- echo " install_scripts('/usr/local/bin')"
- echo
- echo "at the Sage command prompt ('sage:')."
- echo
- echo "If you issued 'make', 'make all', or a similar command, then
the"
- echo "HTML version of the documentation will be built right now."
- echo "Otherwise, if you want to (re)build the HTML documentation,"
- echo "run 'make doc'. To build the PDF version, run 'make doc-pdf'."
- echo
+ echo "
+To install small scripts to directly run Sage's versions of GAP,
+the PARI/GP interpreter, Maxima, or Singular etc. (by typing e.g.
+just 'gap' or 'gp') into a standard 'bin' directory, start Sage
+by typing 'sage' (or './sage') and enter something like
+
+ install_scripts('/usr/local/bin')
+
+at the Sage command prompt ('sage:').
+
+If you issued 'make', 'make all', or a similar command, then the
+HTML version of the documentation will be built right now.
+Otherwise, if you want to (re)build the HTML documentation,
+run 'make doc'. To build the PDF version, run 'make doc-pdf'.
+"
fi
}}}
Are multiline strings not a good idea for "echo"? If this sort of thing
is okay, it makes it much easier to edit the message.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11959#comment:15>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
