#9799: Running "make" in SAGE_ROOT returns the wrong exit code, leading to all
kinds of confusion
---------------------------------------------+------------------------------
   Reporter:  was                            |       Owner:  GeorgSWeber    
       Type:  defect                         |      Status:  positive_review
   Priority:  critical                       |   Milestone:  sage-4.6       
  Component:  build                          |    Keywords:  makefile       
     Author:  Leif Leonhardy, John Palmieri  |    Upstream:  N/A            
   Reviewer:  Jeroen Demeyer                 |      Merged:                 
Work_issues:                                 |  
---------------------------------------------+------------------------------

Comment(by leif):

 Replying to [comment:26 mpatel]:
 > Replying to [comment:24 leif]:
 > > Btw, I wonder if we should at all let the mixed-up output appear on
 the screen (i.e., {{{stdout}}}) when doing ''parallel'' builds. This isn't
 ''that'' easy to handle, because the "decision" to actually perform a
 parallel build is currently (IMHO unnecessarily) made in
 {{{spkg/install}}}. If we want to change that (I'd prefer having just
 ''"Building package xy..."'', ''"Successfully installed package xy"'' /
 ''"Error installing package xy"'' on the screen and in the main log,
 {{{$SAGE_ROOT/install.log}}}), this should of course be addressed on
 another ticket.
 >
 > Would using, e.g.,
 {{{
         @echo '  ACTION  ' $@; command that does the action
 }}}
 > in `Makefile` and `deps` and replacing "pipestatus/tee" with ">>" in
 `deps` help?  Is there any way to keep recording a big, multiplexed log in
 the background, if we still want it?

 I was thinking of ''conditionally'' {{{tee}}}ing (at least) in the top-
 level Makefile (just ''redirecting'' stdout on parallel builds) and
 checking the exit status inside the receipts to print appropriate messages
 to some other file descriptor than stdout in {{{deps}}}.

 Verbosity levels for {{{sage-spkg}}} wouldn't be bad either, especially
 suppressing the verbose {{{tar}}} output is IMHO worth doing, since a lot
 of spkgs contain hundreds or thousands of files (while the actual build
 log is often only a few lines).

 But I must admit I've already forgotten what exactly I'd planned
 yesterday... ;-)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9799#comment:27>
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.

Reply via email to