#7036: rubiks ignores CXX and uses g++ even if CXX is Sun compiler
------------------------------+---------------------------------------------
    Reporter:  drkirkby       |         Owner:  tbd            
        Type:  defect         |        Status:  closed         
    Priority:  major          |     Milestone:  sage-4.3       
   Component:  build          |    Resolution:  fixed          
    Keywords:  GNUism gcc CC  |   Work_issues:                 
    Upstream:  N/A            |      Reviewer:  Mike Hansen    
      Author:  David Kirkby   |        Merged:  sage-4.3.alpha0
Dependencies:                 |  
------------------------------+---------------------------------------------
Description changed by ltw:

Old description:

> Using
>
>     * Solaris 10 update 7 on SPARC
>     * sage-4.1.2.alpha2
>     * Sun Studio 12.1
>     * An updated configure script to allow the Sun compiler to be used
> http://sagetrac.org/sage_trac/ticket/7021
>
> CC was set to the Sun C compiler, CXX to the Sun C++ compiler and
> SAGE_FORTRAN to the Sun Fortran 95 compiler.
>
> rubiks-20070912.p9 totally ignores the setting of CC, and uses gcc which
> it finds in the path. This is unfortunately not an uncommon problem.
>
> {{{
> rubiks-20070912.p9/src/dik/globals.h
> rubiks-20070912.p9/src/dik/permcube.c
> Finished extraction
> ****************************************************
> Host system
> uname -a:
> SunOS swan 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Blade-1000
> ****************************************************
> ****************************************************
> CC Version
> /opt/xxxsunstudio12.1/bin/cc -v
> usage: cc [ options] files.  Use 'cc -flags' for details
> ****************************************************
> Building Rubiks cube solvers
> make[2]: Entering directory
> `/export/home/drkirkby/sage/gcc32/sage-4.1.2.alpha2/spkg/build/rubiks-20070912.p9/src'
> for dir in dietz/cu2 dietz/mcube dietz/solver dik reid; do \
>         (cd ${dir} && make all)\
> done
> make[3]: Entering directory
> `/export/home/drkirkby/sage/gcc32/sage-4.1.2.alpha2/spkg/build/rubiks-20070912.p9/src/dietz/cu2'
> g++ -O2 -c cu2.cpp
> g++ -O2 -c main.cpp
>
> }}}

New description:

 Using

     * Solaris 10 update 7 on SPARC
     * sage-4.1.2.alpha2
     * Sun Studio 12.1
     * An updated configure script to allow the Sun compiler to be used
 #7021

 CC was set to the Sun C compiler, CXX to the Sun C++ compiler and
 SAGE_FORTRAN to the Sun Fortran 95 compiler.

 rubiks-20070912.p9 totally ignores the setting of CC, and uses gcc which
 it finds in the path. This is unfortunately not an uncommon problem.

 {{{
 rubiks-20070912.p9/src/dik/globals.h
 rubiks-20070912.p9/src/dik/permcube.c
 Finished extraction
 ****************************************************
 Host system
 uname -a:
 SunOS swan 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Blade-1000
 ****************************************************
 ****************************************************
 CC Version
 /opt/xxxsunstudio12.1/bin/cc -v
 usage: cc [ options] files.  Use 'cc -flags' for details
 ****************************************************
 Building Rubiks cube solvers
 make[2]: Entering directory
 
`/export/home/drkirkby/sage/gcc32/sage-4.1.2.alpha2/spkg/build/rubiks-20070912.p9/src'
 for dir in dietz/cu2 dietz/mcube dietz/solver dik reid; do \
         (cd ${dir} && make all)\
 done
 make[3]: Entering directory
 
`/export/home/drkirkby/sage/gcc32/sage-4.1.2.alpha2/spkg/build/rubiks-20070912.p9/src/dietz/cu2'
 g++ -O2 -c cu2.cpp
 g++ -O2 -c main.cpp

 }}}

--

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