On Sep 24, 10:42 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 9/24/07, didier deshommes <[EMAIL PROTECTED]> wrote:
>
> > Some build notes:
> > - Singular needs "-lcurses" whenever "-lreadline" is specified. Using
> > it from the console still fails for me.
It depends how readline is build. Many times -ltermcap should fix the
problem, but I got Singular to build and run without problems on
Solaris 9/10 Sparc and Solaris 10 Opteron. Another solution might be
to build ncurses, but I would have to look at the beautiful and well
structured Singular build system 8)
>
> Thanks.
>
> > - clisp won't build but I noticed that blastwave.org has a binary
> > version 2.39 so I installed that and maxima detected it.
I think the trick to building clisp on Solaris is to use a gcc 3.4 and
pass -DNOGENERATIONALGC or something during the build. That is at
least the workaround on NetBSD and when I build Sage's clisp on
Solaris 9 the last time it crashes during the first invocation of the
garbage collector. I reported the problem to the clisp development
list but never got a reply.
> > - to build matplotlib, python needs this fix:
> >http://www.scipy.org/Cookbook/Matplotlib/CompilingMatPlotLibOnSolaris...
Interesting, never had that problem.
> > I did have a spkg wich that tried to get around that...
> > - quaddouble: I re-enabled your rqdf_fix.h to get around isinf(), INFINITY,
> > etc.
> > - I have not installed scipy because I don't know how to point
> > sage_fortran.bin to my fortran compiler. I'm sure the solution simple
> > though...
>
> export SAGE_FORTRAN=`which your_fortran`
>
Easiest is to symbolically link gfortran or g95 to g77, otherwise
scipy prefers the SunPro f90. The export works for Lapack/BLAS but I
am not sure it does the trick for scipy. Haven't tried recently,
though. Best thing might be to make scipy look for g95/gfortran on
Solaris, too.
> > Tests that failed:
>
> Yikes!
>
>
>
> > sage -t algebras/free_algebra_quotient.py
> > sage -t calculus/calculus.py
> > sage -t ext/interactive_constructors_c.pyx
> > sage -t functions/constants.py
> > sage -t functions/functions.py
> > sage -t functions/transcendental.py
> > sage -t geometry/lattice_polytope.py
> > sage -t interfaces/gap.py
> > sage -t interfaces/singular.py
> > sage -t lfunctions/lcalc.py
I got a fix for lcalc. Need to send it in :)
> > sage -t lfunctions/sympow.py
No fix for Sympow on Solaris with Intel/AMD chips so far, but I
believe that the problem is that sympow detects an Intel/AMD cpu and
uses special assembly flags to use the extended FPU precision, while
the fallback mode should be used.
> > sage -t matrix/matrix2.pyx
> > sage -t matrix/matrix_integer_dense.pyx
> > sage -t matrix/matrix_mpolynomial_dense.pyx
> > sage -t matrix/matrix_space.py
> > sage -t modular/ssmod/ssmod.py
> > sage -t plot/plot.py
> > sage -t rings/number_field/number_field.py
> > sage -t rings/number_field/number_field_element.pyx
> > sage -t rings/number_field/number_field_ideal_rel.py
> > sage -t rings/polynomial/groebner_fan.py
> > sage -t rings/polynomial/multi_polynomial_element.py
> > sage -t rings/polynomial/multi_polynomial_ideal.py
> > sage -t rings/polynomial/multi_polynomial_ideal_libsingular.pyx
> > sage -t rings/polynomial/multi_polynomial_libsingular.pyx
> > sage -t rings/polynomial/multi_polynomial_ring.py
> > sage -t rings/polynomial/multi_polynomial_ring_generic.pyx
> > sage -t rings/polynomial/polynomial_element.pyx
> > sage -t rings/polynomial/polynomial_quotient_ring.py
> > sage -t rings/polynomial/polynomial_quotient_ring_element.py
> > sage -t rings/polynomial/polynomial_singular_interface.py
> > sage -t rings/polynomial/term_order.py
> > sage -t rings/polynomial/toy_buchberger.py
> > sage -t rings/complex_double.pyx
> > sage -t rings/homset.py
> > sage -t rings/morphism.py
> > sage -t rings/power_series_ring.py
> > sage -t rings/quotient_ring.py
> > sage -t rings/quotient_ring_element.py
> > sage -t rings/real_double.pyx
> > sage -t rings/real_rqdf.pyx
> > sage -t rings/ring.pyx
> > sage -t schemes/elliptic_curves/ell_padic_field.py
> > sage -t schemes/elliptic_curves/ell_rational_field.py
> > sage -t schemes/generic/affine_space.py
> > sage -t schemes/generic/algebraic_scheme.py
> > sage -t schemes/generic/divisor.py
> > sage -t schemes/generic/morphism.py
> > sage -t schemes/generic/projective_space.py
> > sage -t schemes/hyperelliptic_curves/hyperelliptic_padic_field.py
> > sage -t schemes/plane_curves/affine_curve.py
> > sage -t schemes/plane_curves/constructor.py
> > sage -t schemes/plane_curves/curve.py
> > sage -t schemes/plane_curves/projective_curve.py
> > sage -t structure/element.pyx
>
Overall I am down to 17 failed tests and I believe that at least some
of them might be related to the size of various int types. I will
investigate those down the road as I come back from SD5, but if
anybody else wants to try feel free to send in patches ;)
> > > didier
>
> > > > Cheers,
>
> > > > Michael
>
Cheers,
Michael
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
