#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     |          Keywords:             
Work issues:            |   Report Upstream:  N/A        
  Reviewers:            |           Authors:             
  Merged in:            |      Dependencies:             
   Stopgaps:            |  
------------------------+---------------------------------------------------
 Sometimes, a system-wide GCC can be configured to use a different linker
 than simply `ld` (using `configure --with-ld=/path/to/linker). The path to
 the linker used by GCC can be discovered by
 {{{
 buildbot@mark:~$ gcc -print-file-name=ld
 /usr/local/binutils-2.22/sparc-SunOS-ultrasparc3-gcc-4.6.2-without-
 zlib/bin/ld
 }}}

 Unfortunately, there can be an inconsistency between `$LD` and the linker
 used by GCC, leading to build failures. We should do the following:
 1. If `$LD` is unset, set it to `$CC -print-file-name=ld` by default
 instead of `ld`.
 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).

 Take care to support the case that `$CC` doesn't support the `-print-file-
 name` option.

 ------

 Analogously, the same for the assembler `$AS`.

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