Martin Albrecht wrote:
> I built 2.5.alpha3 over night under Cygwin, it builds if the four remaining
> patches by Michael Abshoff are applied:
>
> 1) sqlite3 fix on cygwin - needs testing on non-cygwin
> +++++++++++++++++++++++++++++
> http://fsmath.mathematik.uni-dortmund.de/~mabshoff/patches/sage-2.5.0-alpha2-fix-sqlite-on-cygwin.patch
>
> 2) gdmodule fix on cygwin - needs to be fixed by using $UNAME
> +++++++++++++++++++++++++++++
> http://fsmath.mathematik.uni-dortmund.de/~mabshoff/patches/sage-2.5.0-alpha2-fix-gdmodule-on-cygwin.patch
>

Before applything this patch just throw the second hunk away. I put it
in after a libsingular build nuked my local/lib and I no longer had a
$UNAME. Providing a unified Setup.py is on my ToDo list (see
http://www.sagemath.org:9001/MichaelAbshoff )

> 3) quadmodule fix on cygwin
> +++++++++++++++++++++++++++++
> http://fsmath.mathematik.uni-dortmund.de/~mabshoff/patches/sage-2.5.0-alpha2-fix-quaddouble-on-cygwin.patch
>
> 4) NAN and SYSTEM wfix for ring_qdfp
> +++++++++++++++++++++++++++++
> http://fsmath.mathematik.uni-dortmund.de/~mabshoff/patches/sage-2.5.0-alpha2-add-NAN-and-INIFINITY-on-cygwin.patch
>
> I made a HG patch for patch 4 (NAN) as it applies to code under version
> control. This HG patch can be found at
>
>    /home/malb/rqdf.hg
>
> I couldn't run "make test" as it would have taken 5 hours.
>

Three remarks:

1. patch 3) and/or 4)  probably caused the following doc test failure:
sage -t  devel/sage-main/sage/functions/constants.py
**********************************************************************
File "constants.py", line 184:
    sage: RQDF(a)
Exception raised:
    Traceback (most recent call last):
      File "/sage-2.5.alpha2/local/lib/python2.5/doctest.py", line
1212, in __run
        compileflags, 1) in test.globs
      File "<doctest __main__.example_0[56]>", line 1, in <module>
        RQDF(a)###line 184:
    sage: RQDF(a)
      File "real_rqdf.pyx", line 172, in
real_rqdf.RealQuadDoubleField_class.__call__
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2446, in _real_rqdf_
        return self.simplify()._real_rqdf_(field)
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2447, in _real_rqdf_
        rops = [op._real_rqdf_(field) for op in self._operands]
      File "/sage-2.5.alpha2/local/lib/python2.5/site-packages/sage/
calculus/calculus.py", line 2448, in _real_rqdf_
        return self._operator(*rops)
      File "element.pyx", line 473, in element.ModuleElement.__add__
      File "element.pyx", line 495, in element.ModuleElement._add_c
      File "real_rqdf.pyx", line 669, in
real_rqdf.QuadDoubleElement._add_c_impl
      File "real_rqdf.pyx", line 352, in
real_rqdf.QuadDoubleElement._new
    SystemError: Python/getargs.c:1270: bad argument to internal
function
**********************************************************************
1 items had failures:
   1 of  64 in __main__.example_0
***Test Failed*** 1 failures.
For whitespace errors, see the file .doctest_constants.py
         [16.7 s]

2. matplotlib is probably effected by the issue reported cwitty
(matplotlib is linked against a non-sage version of libpng) - at least
I hope that is it :)

E:\cygwin\sage-2.5.alpha2\local\bin\python.exe: *** fatal error -
unable to remap E:\cygwin\sage-2.5.alpha2\local\lib\python2.5\site-
packages\matplotlib\_ns_image.dll to same address as
parent(0x1B0D0000) != 0x1B310000

3. sympow doesn't work. William stated that it never did, I got some
hints by the author how to fix this, but this will be past 2.5.0 due
to time constraints and due to that sympow is a rather exotic piece of
code.

> +=+=+=+=+
>  SINGULAR
> +=+=+=+=+
>
> I have uploaded yet another spkg which should finally build on all platforms
> to
>
>    /home/malb/pkgs/singular-3-0-2-20070508.spkg
>
> . Also an updated libsingular.hg is needed which can be found at
>
>   /home/malb/pkgs/libsingular.hg
>
> . However I couldn't test the libsingular SAGE code because I couldn't import
> MPolynomialRing_libsingular and sage.libs.singular.singular for some
> mysterious reason. When trying to
>
> import sage.libs.singular.singular
>
> under CYGWIN (and under CYGWIN only) I get a "No such file or directory" error
> message without any indication which file is missing. Of course, there is a
> file sage/libs/singular/singular.dll.
>
> Thoughts?
> Martin
>
> PS: The usual Singular expect interface works, though.
>
> --
> name: Martin Albrecht
> _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _www: http://www.informatik.uni-bremen.de/~malb
> _jab: [EMAIL PROTECTED]


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

Reply via email to