#18710: Move some make targets to build/Makefile
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.8
Component: build | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/move_some_make_targets_to_build_makefile|
5b6ec50788f2cd19f575adf5f2725d77c4ba6cc3
Dependencies: #18533, #18715, | Stopgaps:
#18716 |
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
OK, let me try again:
> Can't you just move this logging to the other makefile?
There is already logging in the individual rules in `build/Makefile`. This
is logging number 1.
The logging to `install.log` from `Makefile` is logging number 2.
I don't see where a "triple logging" could come from.
Note that `install.log` contains information which is not available from
the individual log files:
1. a listing of environment variables at the start of the build, and other
output from `build/install`.
2. timing information: it shows all commands in parallel as they are
executed. This is actually a feature, since it allows debugging race
conditions. With just the individual files, that information is lost.
--
Ticket URL: <http://trac.sagemath.org/ticket/18710#comment:34>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
