Michael Brickenstein wrote: > Hello! > Thanks for your efforts. > The problem is, that for CXX then SUN-compiler was used. > > You can pass the CXX > scons CXX='g++' > > custom.py > CXX='g++' > > At the moment, we don't know, why Suns compiler is used for C++, while > gcc is used for C. > Michael
Actually, g++ is used for some C++ file, but Sun's compiler for others. Also Sun's C++ compiler CC is used to build the library. Is there any way you could change this to the flags CC, CXX and any others needed are inherited properly, rather than hard-coding the compiler? I suspect AR would be needed, and perhaps CFLAGS, CXXFLAGS and possibly others. Hard-coding the compiler to g++ would create problems if someone wanted to specify a particular version of the compiler. That will also fail if we want to build the code with Sun's compiler. Dave > On 15 Jul., 08:22, Minh Nguyen <nguyenmi...@gmail.com> wrote: >> Hi David, >> >> On Tue, Jul 14, 2009 at 8:16 PM, Dr. David >> >> Kirkby<david.kir...@onetel.net> wrote: >> >> <SNIP> >> >> >> >>>> I'm building Sage 4.1 on t2 at the moment; it has been going on for >>>> hours now. This build uses David Kirkby's updated spkgs: >>>> polybori-0.5rc.p9.spkg at >>>> http://sagetrac.org/sage_trac/ticket/6437 >>>> pari-2.3.3.p1.spkg at >>>> http://sagetrac.org/sage_trac/ticket/6445 >>>> ntl-5.4.2.p9.spkg at >>>> http://sagetrac.org/sage_trac/ticket/6443 >>>> So far, ATLAS is still compiling and it looks like that ATLAS will >>>> build successfully. >>> Thank you. Perhaps >>> ATLAS takes AGES to build unfortunately. I hope to resolve that at some >>> time, as some architectual defaults can be applied. It's not helped I >>> can't work out how to keep the intermediate files generated by the build >>> of ATLAS, which are needed to generate the architectural defaults. What >>> I thought was the correct syntax to do this fails to work. Also my >>> attempts to hard-code a script have failed to stop the files being >>> deleted - see my thread 'Can I keep build data once a package is >>> installed ok?' >>> You might need other fixes too. If something does not build, check out >>> this directory of mine. >>> http://sage.math.washington.edu/home/kirkby/Solaris-fixes/ >>> In particular you are likely to need a znpoly patch: >>> http://sagetrac.org/sage_trac/ticket/6443 >>> A flint patch, which has already received positive review, so does not >>> need reviewing. >>> http://sagetrac.org/sage_trac/ticket/6451 >>> You need to be careful with flint, as flint *appears* to install >>> correctly, making the file $SAGE_HOME/spkg/installed/flint-xxx >> After hours of compilation time on t2, I got an install error. Well, >> FLINT built OK as were ATLAS, Pari and NTL. The compilation died when >> trying to build PolyBori, i.e. polybori-0.5rc.p9.spkg. The full >> install log is at >> >> http://sage.math.washington.edu/home/mvngu/patch/solaris-install.log >> >> -- >> Regards >> Minh Van Nguyen > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send 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 -~----------~----~----~----~------~----~------~--~---
