Yes, I believe so too, however, the latest version of gcc 4.5.0 causes a build error with R, so I'm compiling and testing an intermediate version , gcc-4.3.5.
On Mon, Jun 28, 2010 at 9:46 PM, Robert Bradshaw < rober...@math.washington.edu> wrote: > On Jun 28, 2010, at 9:12 AM, caleb wrote: > > I've attached the output of gcc -v to the discussion, but I notice now >> that it was mentioned in some earlier discussion that gcc 4.1.0 was >> blacklisted. The version of gcc is the only difference that I notice >> between the cluster that complies Sage flawlessly and this one. >> > > Well, the answer is to us a more recent gcc (as 4.1.0 clearly has a bug in > it). > > >> Caleb >> >> On Jun 27, 1:54 am, Robert Bradshaw <rober...@math.washington.edu> >> wrote: >> >>> On Jun 27, 2010, at 1:40 AM, caleb miles wrote: >>> >>> Hello, >>>> >>> >>> I am attempting to compile SAGE 4.4.4 on an OpenSUSE cluster for >>>> local use, however, the build process fails while installing Cython, >>>> and I have attached the portion of install.log corresponding to the >>>> build process. >>>> >>> >>> Thanks. The key lines seem to be >>> >>> /nano/scratch/camiles/binaries/sage-4.4.4/spkg/build/cython-0.12.1/src/ >>> Cython/Compiler/Parsing.c: In function >>> ‘__pyx_f_6Cython_8Compiler_7Parsing_flatten_parallel_assignments’: >>> /nano/scratch/camiles/binaries/sage-4.4.4/spkg/build/cython-0.12.1/src/ >>> Cython/Compiler/Parsing.c:17225: internal compiler error: in >>> merge_alias_info, at tree-ssa-copy.c:235 >>> Please submit a full bug report, >>> with preprocessed source if appropriate. >>> See <URL:http://www.suse.de/feedback> for instructions. >>> error: command 'gcc' failed with exit status 1 >>> >>> i.e. a compiler error. Can you do gcc -v? >>> >>> The cluster has four processors, on the administration node I am >>>> working on of the type: >>>> >>> >>> processor : 0 >>>> vendor_id : GenuineIntel >>>> cpu family : 6 >>>> model : 15 >>>> model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz >>>> stepping : 6 >>>> cpu MHz : 2327.554 >>>> cache size : 4096 KB >>>> physical id : 0 >>>> siblings : 2 >>>> core id : 0 >>>> cpu cores : 2 >>>> fdiv_bug : no >>>> hlt_bug : no >>>> f00f_bug : no >>>> coma_bug : no >>>> fpu : yes >>>> fpu_exception : yes >>>> cpuid level : 10 >>>> wp : yes >>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr >>>> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm >>>> pbe nx lm constant_tsc pni monitor ds_cpl v >>>> mx est tm2 cx16 xtpr lahf_lm >>>> bogomips : 4658.82 >>>> >>> >>> further information about the computer >>>> >>> >>> Linux version 2.6.16.27-0.9-chpc (ge...@buildhost) (gcc version >>>> 4.1.0 (SUSE Linux)) #1 SMP Tue Mar 27 15:24:37 MDT 2007 >>>> >>> >>> I was able to compile SAGE version 3.4.3 on another similar cluster >>>> which is working wonderfully, so I was rather surprised by the >>>> failure in this case. Any help would be greatly appreciated. >>>> >>> >>> Sincerely, >>>> >>> >>> Caleb Miles >>>> -- >>>> Cahn's Axiom: >>>> When all else fails, read the instructions. >>>> >>> >>> -- >>>> 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<sage-devel%2bunsubscr...@googlegroups.com> >>>> For more options, visit this group athttp:// >>>> groups.google.com/group/sage-devel >>>> >>>> URL:http://www.sagemath.org >>>> <cython_fail.log> >>>> >>> > -- 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 URL: http://www.sagemath.org
