J Elaych wrote:
>> I just upgraded to karmic and the exact same thing happened.
>> Please tell me (in terms an idiot can understand:-) how to get
>> the Sage make command to use a different gcc.
>>
>>
> 
> Good question, and I hope somebody else can improve my response.
> I didn't find a gcc switching tool like I've used in the distant past,
> so I went to /usr/bin, did an 'ls -l gc*' and noted that gcc and
> something else (gcov?) pointed to the gcc-4.4 versions.  There were
> also gcc-4.3 versions, so I just did


For what it is worth, I have built Sage 4.1.1.rc0 with gcc 4.4.0 on 
SPARC. Pari built fine.

In theory, setting

CC=/path/to/what/C/compiler/you/want
CXX=/path/to/what/C++/compiler/you/want
SAGE_FORTRAN=/path/to/what/Fortran/compiler/you/want

should allow you to use any gcc.

But in practice I don't think it will. I've tried doing this with the 
Sun compiler, and find that some parts of Sage build with gcc even 
though CC is specified as the Sun compiler. Hence some parts of Sage are 
ignoring whatever CC is set to.

The only one I can see to use a specific version of gcc is to make sure 
that version is the first gcc in your path. Then it will be found before 
any other version.

Dave

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to