#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: Leif Leonhardy | Author: John Palmieri
Merged: | Dependencies:
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:22 jhpalmieri]:
> Why can't I just do
{{{
build-serial: export SAGE_PARALLEL_SPKG_BUILD = no
build-serial: build
}}}
Well, you could. You could also add
{{{
#!make
export SAGE_PARALLEL_SPKG_BUILD
}}}
somewhere in the Makefile (preferably near the top), or use
{{{
#!make
EXPORTS = SAGE_PARALLEL_SPKG_BUILD="$(SAGE_PARALLEL_SPKG_BUILD)" \
SAGE_FOO="$(SAGE_FOO)"
...
bar:
env $(EXPORTS) ./baz
}}}
> Or is this too specific to GNU make?
I don't care much, although I prefer not using GNUisms if there's a
''simple'' alternative. AFAIK older ''GNU'' makes don't support `export`
either, but I haven't checked since when they do.
[[BR]]
> > Do we mention LC_ALL=C (or e.g. LC_MESSAGES=en_US.utf8) for submitting
error logs?
>
> I don't think so, and I'm not planning to add anything about it.
Hmmmm. :(
[[BR]]
> Re `TROUBLESHOOTING.txt`: we could instead have a structure more like
many GNU projects: a boilerplate README and then a file INSTALL with
specific instructions.
TROUBLESHOOTING is much more explicit. Most INSTALL files shipped are
just templates, so it's quite likely that people wouldn't read them
either. We also have the (longer) Sage Installation Guide; I was aiming
at a short plain text file purely on topic, i.e. common issues (which
might get updated more frequently and easily), and how and where to report
build failures / ask for build-related support.
[[BR]]
> While we're off-topic: Is the top-level `install.log` any use as it is
right now?
I'd keep at least the file; whether it makes sense to dump it to the
screen -- especially in parallel builds -- is another question.
> For changing the format of install.log etc., we could write to the
individual log files as part of sage-spkg, instead of when sage-spkg is
called by sage-sage or spkg/install.
That's what I suggested more than a year ago. :-) Also, a large amount of
the output are distutils' "copying ..." messages, and ECL (also when
building Maxima) is far too verbose, too.
We don't lose much if we move the logging from `deps` to `sage-spkg`. The
latter should take a couple of logging-related parameters like
`--logfile=`, `--logfd=`, `--loglevel=`, with the possibility to specify
more than one logfile or file descriptor, with the same or different log
levels.
Unfortunately `sage-spkg` is a hot spot; it needs work in all places.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11959#comment:25>
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.
