#14296: Force consistency of $LD and $AS with $CC
----------------------------+-----------------------------------------------
       Reporter:  jdemeyer  |         Owner:  GeorgSWeber
           Type:  defect    |        Status:  new        
       Priority:  major     |     Milestone:  sage-5.9   
      Component:  build     |    Resolution:             
       Keywords:            |   Work issues:             
Report Upstream:  N/A       |     Reviewers:             
        Authors:            |     Merged in:             
   Dependencies:            |      Stopgaps:             
----------------------------+-----------------------------------------------

Comment (by leif):

 Replying to [ticket:14296 jdemeyer]:
 > Unfortunately, there can be an inconsistency between `$LD` and the
 linker used by GCC, leading to build failures.

 This affects only a few spkgs.  IMHO we should fix these, by changing
 their `spkg-install` scripts, or -- much better -- patching the upstream
 sources and reporting the fixes upstream.

 > We should do the following:
 > 1. If `$LD` is unset, set it to `$CC -print-file-name=ld` by default
 instead of `ld`.

 Agreed.

 > 2. If `$LD` is set and the value differs from `$CC -print-file-name=ld`,
 force building of the GCC spkg (define these values to be equal if the
 output of `command -v VALUE` is equal).

 That's a bit overkill.  Ok for a buildbot, but otherwise we should just
 issue a warning (or, more complicated, error  out unless some override
 setting is active).

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