On Feb 5, 3:29 pm, Jaap Spies <j.sp...@hccnet.nl> wrote:
> Gokhan Sever wrote:
>
> > On Jan 24, 10:59 am, gsever<gokhanse...@gmail.com>  wrote:
> >> Hello,
>
> >> Am I getting the similar error of FC12 (i686) binaries not pushed in
> >> the download section?
>
> >> [gse...@ccn sage-4.3.1]$ uname -a
> >> Linux ccn 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21 06:04:56 UTC
> >> 2009 i686 i686 i386 GNU/Linux
>
> >> [gse...@ccn sage-4.3.1]$ cat /proc/cpuinfo
> >> processor       : 0
> >> vendor_id       : GenuineIntel
> >> cpu family      : 6
> >> model           : 23
> >> model name      : Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz
> >> stepping        : 6
> >> cpu MHz         : 2500.000
> >> cache size      : 6144 KB
> >> physical id     : 0
> >> siblings        : 2
> >> core id         : 0
> >> cpu cores       : 2
> >> apicid          : 0
> >> initial apicid  : 0
> >> 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 arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
> >> tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
> >> flexpriority
> >> bogomips        : 4986.77
> >> clflush size    : 64
> >> power management:
>
> >> processor       : 1
> >> vendor_id       : GenuineIntel
> >> cpu family      : 6
> >> model           : 23
> >> model name      : Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz
> >> stepping        : 6
> >> cpu MHz         : 800.000
> >> cache size      : 6144 KB
> >> physical id     : 0
> >> siblings        : 2
> >> core id         : 1
> >> cpu cores       : 2
> >> apicid          : 1
> >> initial apicid  : 1
> >> 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 arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
> >> tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
> >> flexpriority
> >> bogomips        : 4986.03
> >> clflush size    : 64
> >> power management:
>
> >> Successfully installed r-2.9.2
> >> Running the test suite.
> >> make[2]: Entering directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src'
> >> make[3]: Entering directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests'
> >> make[4]: Entering directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests'
> >> make[4]: warning: -jN forced in submake: disabling jobserver mode.
> >> make[5]: Entering directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests/Examples'
> >> make[5]: warning: -jN forced in submake: disabling jobserver mode.
>
> >> Collecting examples for package ‘base’
> >> Running examples in package ‘base’
>
> >> Collecting examples for package ‘tools’
> >> Running examples in package ‘tools’
>
> >> Collecting examples for package ‘utils’
> >> Running examples in package ‘utils’
> >> Error: testing 'utils' failed
> >> Execution halted
> >> make[5]: *** [test-Examples-Base] Error 1
> >> make[5]: Leaving directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests/Examples'
> >> make[4]: *** [test-Examples] Error 2
> >> make[4]: Leaving directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests'
> >> make[3]: *** [test-all-basics] Error 1
> >> make[3]: Leaving directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src/tests'
> >> make[2]: *** [check] Error 2
> >> make[2]: Leaving directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg/build/r-2.9.2/src'
> >> Error while running the R testsuite ... exiting
> >> *************************************
> >> Error testing package ** r-2.9.2 **
> >> *************************************
> >> sage: An error occurred while testing r-2.9.2
> >> Please email sage-develhttp://groups.google.com/group/sage-devel
> >> explaining the problem and send the relevant part of
> >> of /home/gsever/Desktop/python-repo/sage-4.3.1/install.log.  Describe
> >> your computer, operating system, etc.
> >> If you want to try to fix the problem yourself, *don't* just cd to
> >> /home/gsever/Desktop/python-repo/sage-4.3.1/spkg/build/r-2.9.2 and
> >> type 'make check' or whatever is appropriate.
> >> Instead, the following commands setup all environment variables
> >> correctly and load a subshell for you to debug the error:
> >> (cd '/home/gsever/Desktop/python-repo/sage-4.3.1/spkg/build/r-2.9.2'
> >> &&  '/home/gsever/Desktop/python-repo/sage-4.3.1/sage' -sh)
> >> When you are done debugging, you can type "exit" to leave the
> >> subshell.
> >> make[1]: *** [installed/r-2.9.2] Error 1
> >> make[1]: Leaving directory `/home/gsever/Desktop/python-repo/
> >> sage-4.3.1/spkg'
>
> >> real    124m58.197s
> >> user    125m3.126s
> >> sys     11m14.695s
> >> Error building Sage.
>
> > Testing sage-4.3.2.rc0 with export SAGE_CHECK="yes" yields a different
> > set of errors this time:
>
> > Successfully installed pyprocessing-0.52.p0
>
> OK, pyprocessing is in principle out iirc.
>
> Are you building with SAGE_CHECK = something non empty?
> I think this will fail not only here.
>
> I would do a unset SAGE_CHECK,
> and try again.
>
> Jaap
>
> > Running the test suite.
> > /home/gsever/Desktop/python-repo/sage-4.3.2.rc0/local/bin/python:
> > processing.tests is a package and cannot be directly executed
> > *************************************
> > Error testing package ** pyprocessing-0.52.p0 **
> > *************************************
> > sage: An error occurred while testing pyprocessing-0.52.p0
> > Please email sage-develhttp://groups.google.com/group/sage-devel
> > explaining the problem and send the relevant part of
> > of /home/gsever/Desktop/python-repo/sage-4.3.2.rc0/install.log.
> > Describe your computer, operating system, etc.
> > If you want to try to fix the problem yourself, *don't* just cd to
> > /home/gsever/Desktop/python-repo/sage-4.3.2.rc0/spkg/build/
> > pyprocessing-0.52.p0 and type 'make check' or whatever is appropriate.
> > Instead, the following commands setup all environment variables
> > correctly and load a subshell for you to debug the error:
> > (cd '/home/gsever/Desktop/python-repo/sage-4.3.2.rc0/spkg/build/
> > pyprocessing-0.52.p0'&&  '/home/gsever/Desktop/python-repo/
> > sage-4.3.2.rc0/sage' -sh)
> > When you are done debugging, you can type "exit" to leave the
> > subshell.
> > make[1]: *** [installed/pyprocessing-0.52.p0] Error 1
> > make[1]: Leaving directory `/home/gsever/Desktop/python-repo/
> > sage-4.3.2.rc0/spkg'
>
> > real       117m40.871s
> > user       113m41.865s
> > sys        10m53.131s
> > Error building Sage.

Running "make test" this time. I will update once its done.

-- 
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

Reply via email to