#10572: compiler/binutils wrapper
---------------------------------------------------+------------------------
       Reporter:  vbraun                           |         Owner:  
GeorgSWeber 
           Type:  enhancement                      |        Status:  
needs_review
       Priority:  major                            |     Milestone:  sage-5.10  
 
      Component:  build                            |    Resolution:             
 
       Keywords:  compiler gcc wrapper rpath spkg  |   Work issues:             
 
Report Upstream:  N/A                              |     Reviewers:             
 
        Authors:  Volker Braun                     |     Merged in:             
 
   Dependencies:                                   |      Stopgaps:             
 
---------------------------------------------------+------------------------

Comment (by vbraun):

 Ok, maybe a new attempt is in order.

 I'll try to be more gradual. For now, keep `LD_LIBRARY_PATH` but use the
 compilerwrapper to rewrite rpaths. I added the feature to overwrite
 `LD_LIBRARY_PATH` with `SAGE_OLD_LD_LIBRARY_PATH` before calling gcc/ld,
 so at least the nasty library version clashes in the compiler are avoided.

 We need to figure out what to do if sage builds its own gcc since only one
 gcc can live in `$SAGE_LOCAL/bin`. I would be in favor of compiling our
 own gcc with some pre/postfix as `$SAGE_LOCAL/bin/gcc-sage`. The
 compilerwrapper can then easily switch between this gcc and the host one,
 if desired. Thoughts?

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10572#comment:32>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to