[sage-devel] Help compiling on supercomputer!

2014-02-09 Thread Kate Stange
Hi all,

I just recently received my allocation on the University of Boulder's
Research Computing cluster, with the supercomputer JANUS:

https://www.rc.colorado.edu/

And so I logged in and compiled sage from source on one of the JANUS
compile nodes (6.1.1, downloaded yesterday).

I ran make on one node with 12 threads, but after about 20 minutes it
failed on git.  I'd love to have Sage working on there, so I'm hoping
someone out there might be able to make a suggestion.  I can contact RC
help about this, but I thought it might help to have a few responses here
about what to ask them specifically.

Here's the relevant bit of git's log:

make[4]: Entering directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
/usr/bin/perl Makefile.PL PREFIX='/projects/kast5807/sage-6.1.1/local'
INSTALL_BASE=''
--localedir='/projects/kast5807/sage-6.1.1/local/share/locale'
Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains:
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/
vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3.
BEGIN failed--compilation aborted at Makefile.PL line 3.
make[4]: *** [perl.mak] Error 2
make[4]: Leaving directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
make[3]: *** [perl/perl.mak] Error 2
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src'
Error building git.

Thanks!

 Katherine Stange
Department of Mathematics ~ University of Colorado, Boulder
( Campus Box 395, Boulder, Colorado 80309 ~ ksta...@math.colorado.edu )
math: http://math.katestange.net/
photos: http://pixel.katestange.net/

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] Help compiling on supercomputer!

2014-02-09 Thread Kate Stange
 http://pixel.katestange.net/

Hi all,

I just recently received my allocation on the University of Boulder's
Research Computing cluster, with the supercomputer JANUS:

https://www.rc.colorado.edu/

And so I logged in and compiled sage from source on one of the JANUS
compile nodes (6.1.1, downloaded yesterday).

I ran make on one node with 12 threads, but after about 20 minutes it
failed on git.  I'd love to have Sage working on there, so I'm hoping
someone out there might be able to make a suggestion.  I can contact RC
help about this, but I thought it might help to have a few responses here
about what to ask them specifically.

Here's the relevant bit of git's log:

make[4]: Entering directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
/usr/bin/perl Makefile.PL PREFIX='/projects/kast5807/sage-6.1.1/local'
INSTALL_BASE=''
--localedir='/projects/kast5807/sage-6.1.1/local/share/locale'
Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains:
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/
vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3.
BEGIN failed--compilation aborted at Makefile.PL line 3.
make[4]: *** [perl.mak] Error 2
make[4]: Leaving directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
make[3]: *** [perl/perl.mak] Error 2
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory
`/projects/kast5807/sage-6.1.1/local/var/tmp/sage/build/git-1.8.4.4/src'
Error building git.

Thanks!

 Katherine Stange
Department of Mathematics ~ University of Colorado, Boulder
( Campus Box 395, Boulder, Colorado 80309 ~ ksta...@math.colorado.edu )
math: http://math.katestange.net/
photos: http://pixel.katestange.net/

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] ATLAS developer request

2008-02-11 Thread Kate

On the math-atlas-devel list, there is the following request from
the ATLAS project leader:

: Here at UTSA, we are making a poster showing research done in the
department.
: I've been asked to provide a picture of ATLAS at work, if possible.
Does
: anyone out there use ATLAS for visualization, or have a graphic of
something
: like an adaptive mesh problem that uses ATLAS underneath that they
wouldn't
: mind providing for this use? Anything real  pretty that uses ATLAS
as
: part of the computation would be great . . .

Since Sage uses ATLAS, and Sage can make pretty pictures, perhaps
someone can suggest something?

Kate

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] 2.10.1, itanium-Linux, and graph_generators.py

2008-02-05 Thread Kate

When I build sage-2.10.1 (using gcc-4.2.2) on my itanium-Linux
box, 'make check' gives

sage -t  devel/sage-main/sage/graphs/graph_generators.py*** ***
Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***

If I edit local/bin/sage-doctest and increase TIMEOUT to 240 (from
180), then when
I run 'make check I get

sage -t  devel/sage-main/sage/graphs/graph_generators.py
 [138.8 s]

Q1. Since 138.8  180, why was the original TIMEOUT not sufficient?

Q2. Should I be worried that I had to raise TIMEOUT to 240?

Kate
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: 2.10.1, itanium-Linux, and graph_generators.py

2008-02-05 Thread Kate

[EMAIL PROTECTED] sage-2.10.1-ia64-Linux]$ time ./sage -t devel/sage-main/
sage/graphs/graph_generators.py
sage -t  devel/sage-main/sage/graphs/graph_generators.py
 [144.7 s]

--
All tests passed!
Total time for all tests: 144.7 seconds

real2m24.827s
user1m38.499s
sys 0m2.192s
[EMAIL PROTECTED] sage-2.10.1-ia64-Linux]$

On Feb 5, 4:23 pm, William Stein [EMAIL PROTECTED] wrote:
 On Feb 5, 2008 1:18 PM, Kate [EMAIL PROTECTED] wrote:





  When I build sage-2.10.1 (using gcc-4.2.2) on my itanium-Linux
  box, 'make check' gives

  sage -t  devel/sage-main/sage/graphs/graph_generators.py*** ***
  Error: TIMED OUT! *** ***
  *** *** Error: TIMED OUT! *** ***

  If I edit local/bin/sage-doctest and increase TIMEOUT to 240 (from
  180), then when
  I run 'make check I get

  sage -t  devel/sage-main/sage/graphs/graph_generators.py
   [138.8 s]

  Q1. Since 138.8  180, why was the original TIMEOUT not sufficient?

 That's really odd.  Could you do

 $ time sage -t  devel/sage-main/sage/graphs/graph_generators.py

 and report the output? Here's what happens on a certain 2.6Ghz core 2 duo mac:

 D-69-91-159-216:d was$ time sage -t sage-main/sage/graphs/graph_generators.py
 sage -t  sage-main/sage/graphs/graph_generators.py
  [38.7 s]

 --
 All tests passed!
 Total time for all tests: 38.7 seconds

 real0m38.775s
 user0m34.011s
 sys 0m2.156s
 D-69-91-159-216:d was$



  Q2. Should I be worried that I had to raise TIMEOUT to 240?

 No, I don't think you should be worried.Itaniums are slow.

  -- William
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] sage-2.9.1.txt file in sage-2.10

2008-01-22 Thread Kate

Is there a good reason why the file 'sage-2.9.1.txt'
is at the top-level of sage-2.10?

Kate
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: Sage 2.10.alpha3 released

2008-01-16 Thread Kate

Michael,

The patch for #1790 is ok,  but after applying the patch for #1791
I now get

./sage -t devel/sage-main/sage/rings/polynomial/polynomial_element.pyx
sage -t  devel/sage-main/sage/rings/polynomial/
polynomial_element.pyx**
File polynomial_element.pyx, line 2644:
sage: p.roots(ring=ComplexIntervalField(200))
Expected:
 
[([1.1673039782614186842560458998548421807205603715254890391400816 ..
1.1673039782614186842560458998548421807205603715254890391400829], 1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] +
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] -
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777... ..
-0.76488443360058472602982318770854173032899665194736756700777...] +
[0.35247154603172624931794709140258105439420648082424733283769... ..
0.35247154603172624931794709140258105439420648082424733283769...]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777454 ..
-0.764884433600584726029823187708541730328996651947367567007772...] -
[0.35247154603172624931794709140258105439420648082424733283769... ..
0.3524715460317262493179470914025810543942064808242473328376934...]*I,
1)]
Got:
 
[([1.1673039782614186842560458998548421807205603715254890391400816 ..
1.1673039782614186842560458998548421807205603715254890391400829], 1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] +
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] -
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777516 ..
-0.76488443360058472602982318770854173032899665194736756700777204] +
[0.35247154603172624931794709140258105439420648082424733283769091 ..
0.35247154603172624931794709140258105439420648082424733283769372]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777454 ..
-0.76488443360058472602982318770854173032899665194736756700777204] -
[0.35247154603172624931794709140258105439420648082424733283769091 ..
0.35247154603172624931794709140258105439420648082424733283769372]*I,
1)]
**
1 items had failures:
   1 of 109 in __main__.example_58
***Test Failed*** 1 failures.
For whitespace errors, see the file .doctest_polynomial_element.pyx
 [6.6 s]
exit code: 256

--

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



[sage-devel] Re: Sage 2.10.alpha3 released

2008-01-16 Thread Kate

Michael,

This fixes the issue.  Thanks!

Kate

On Jan 16, 11:22 am, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 On Jan 16, 5:08 pm, Kate [EMAIL PROTECTED] wrote:

  Michael,

 Hi Kate,

  The patch for #1790 is ok,  but after applying the patch for #1791
  I now get

 I see that I missed one single digit being different. Please try

 http://trac.sagemath.org/sage_trac/attachment/ticket/1790/Sage-2.10.a...

 which should fix the issue hopefully for good.



  ./sage -t devel/sage-main/sage/rings/polynomial/polynomial_element.pyx
  sage -t  devel/sage-main/sage/rings/polynomial/
  polynomial_element.pyx**
  File polynomial_element.pyx, line 2644:
  sage: p.roots(ring=ComplexIntervalField(200))
  Expected:

 SNIP
  --

  Kate

 Cheers,

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



[sage-devel] Re: Sage 2.10.alpha3 released

2008-01-15 Thread Kate

Michael,

sage-2.10.alpha3 fails one test (polynomial_element.pyx) on
both
  x86-Linux (pentium4-fc6)
  x86_64-Linux (Opteron-fc6)

Both were built using gcc-4.2.2

Details follow.

Kate

**
x86-Linux
**

sage -t  devel/sage-main/sage/rings/polynomial/
polynomial_element.pyx**
File polynomial_element.pyx, line 2549:
sage: f.roots(multiplicities=False)
Expected:
[...1.00...*I, 1.00...*I]
Got:
[1.00 + 1.11022302462516e-16*I, 1.12045416424138e-16 +
1.00*I]
**


*
x86_64-Linux
*

sage -t  devel/sage-main/sage/rings/polynomial/
polynomial_element.pyx**
File polynomial_element.pyx, line 2644:
sage: p.roots(ring=ComplexIntervalField(200))
Expected:
 
[([1.1673039782614186842560458998548421807205603715254890391400816 ..
1.1673039782614186842560458998548421807205603715254890391400829], 1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] +
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] -
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777454 ..
-0.76488443360058472602982318770854173032899665194736756700777...] +
[0.35247154603172624931794709140258105439420648082424733283769... ..
0.35247154603172624931794709140258105439420648082424733283769...]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777454 ..
-0.764884433600584726029823187708541730328996651947367567007772...] -
[0.352471546031726249317947091402581054394206480824247332837691... ..
0.35247154603172624931794709140258105439420648082424733283769341]*I,
1)]
Got:
 
[([1.1673039782614186842560458998548421807205603715254890391400816 ..
1.1673039782614186842560458998548421807205603715254890391400829], 1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] +
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([0.1812326987538390180023778112063996871646618462304743773153 ..
0.1812326987538390180023778112063996871646618462304743773341] -
[1.0839541013177106684303444929807665742736402431551156543011306 ..
1.0839541013177106684303444929807665742736402431551156543011344]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777516 ..
-0.76488443360058472602982318770854173032899665194736756700777204] +
[0.35247154603172624931794709140258105439420648082424733283769091 ..
0.35247154603172624931794709140258105439420648082424733283769372]*I,
1),
([-0.76488443360058472602982318770854173032899665194736756700777454 ..
-0.76488443360058472602982318770854173032899665194736756700777204] -
[0.35247154603172624931794709140258105439420648082424733283769091 ..
0.35247154603172624931794709140258105439420648082424733283769372]*I,
1)]
**
File polynomial_element.pyx, line 2666:
sage: p.roots(ring=CIF)
Expected:
[([-1.4142135623730952 .. -1.4142135623730949], 1),
([1.4142135623730949 .. 1.4142135623730952], 1),
([-1.2146389322441827 .. -1.2146389322441821] -
[0.1414250525823937... .. 0.1414250525823939...]*I, 2),
([-0.141425052582393... .. -0.14142505258239376] +
[1.2146389322441821 .. 1.2146389322441827]*I, 2),
([0.141425052582393... .. 0.141425052582393...] -
[1.2146389322441821 .. 1.2146389322441827]*I, 2),
([1.2146389322441821 .. 1.2146389322441827] + [0.14142505258239376 ..
0.14142505258239399]*I, 2)]
Got:
[([-1.4142135623730952 .. -1.4142135623730949], 1),
([1.4142135623730949 .. 1.4142135623730952], 1),
([-1.2146389322441827 .. -1.2146389322441821] -
[0.14142505258239373 .. 0.14142505258239397]*I, 2),
([-0.14142505258239397 .. -0.14142505258239373] +
[1.2146389322441821 .. 1.2146389322441827]*I, 2),
([0.14142505258239376 .. 0.14142505258239397] - [1.2146389322441821 ..
1.2146389322441827]*I, 2), ([1.2146389322441821 .. 1.2146389322441827]
+ [0.14142505258239376 .. 0.14142505258239399]*I, 2)]
**

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

[sage-devel] Re: SAGE 2.10.alpha0 released

2008-01-09 Thread Kate

Michael,

Sage-2.10.alpha0 builds from source (using gcc-4.2.2)
fine for me on

  x86-Linux (pentium4-fc6)
  x86_64-Linux (opteron-fc6)

but fails on ia64-Linux (RH Linux) in flint-1.05 with

Testing _fmpz_poly_mul_karatsuba()... ok
Testing _fmpz_poly_mul_karatsuba_trunc()... ok
Testing _fmpz_poly_mul_karatsuba_trunc_left()... ok
Testing _fmpz_poly_mul_KS()... GNU MP: Cannot reallocate memory
(old_size=8 new_size=4294959128)
./spkg-check: line 51: 11240 Aborted (core dumped) ./
fmpz_poly-test

Kate


On Jan 7, 9:30 pm, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 Hello folks,

 and a new merge cycle has been opened. Every time I finish one they
 pull me back in again ;)

 Anyways, tarball is in

 http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10/

 Inside that directory you see another directory alpha0 which contains
 all updated spkgs as well as all patches. So that way you can keep an
 eye on development and just grab patches and spkgs as they get merged.
 Once I start alpha1 expect that directory to appear there, too.

 As usual I will ask people to do reviews and fix open bugs. Come on
 over to the tracker and do your best. alpha0 was mostly about mem leak
 fixes, I did discover a whole bunch of new ones when I did an audit
 with the help of valgrind of 2.9.3 and with the help of various people
 (see below) we fixed a whole bunch of them. We are getting to the
 point where the number of known leaks is going toward zero, the main
 culprit at the moment is Givaro.

 As usual let us know about any issue you encounter. I am catching some
 sleep now - see you in the morning.

 Cheers,

 Michael

 Merged in alpha0:

 #1092: Willem Jan Palenstijn, Michael Abshoff: small memleaks exposed
by ntl_ZZ_pE
 #1093: Michael Abshoff, Willem Jan Palenstijn: small memleaks exposed
by ntl_ZZ_pX.py
 #1541: Burcin Erocal: improve PolyBoRi integration
 #1544: David Joyner, Rich Morin: SAGE Tutorial nits #2
 #1553: Kiran Kedlaya, Michael Abshoff: SCons related build failure
of PolyBoRi on 64-bit RHEL5
 #1598: Martin Albrecht: fix SIGSEGV in libSINGULAR interface on
Solaris
 #1694: Michael Abshoff, Bill Hart: Update FLINT to 1.05 release
 #1701: Martin Albrecht: attempt to clean up currRing if deallocated
 #1702: Martin Albrecht: fix memleak in fplll.pyx
 #1703: Michael Abshoff: memleak in Singular: one mpz is leaked in
longrat.cc
--~--~-~--~~~---~--~~
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/
-~--~~~~--~~--~--~---



[sage-devel] Re: SAGE 2.10.alpha0 released

2008-01-09 Thread Kate

Michael,

 I found the same bug on an Itanium also with gcc 4.2.2. See

 https://groups.google.com/group/sage-devel/t/a05734c584f012b

Sorry, missed that.

 Another question: I assume we can 
 closehttp://trac.sagemath.org/sage_trac/ticket/1277
 since those two issues you reported there have been resolved. I meant
 to ask for confirmation, but I got side tracked over the last couple
 days :(

Yes, you may close it.  flint built ... just did not pass its tests.

Kate

On Jan 9, 11:23 am, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 On Jan 9, 5:15 pm, Kate [EMAIL PROTECTED] wrote:

  Michael,

 Hi Kate,

  Sage-2.10.alpha0 builds from source (using gcc-4.2.2)
  fine for me on

x86-Linux (pentium4-fc6)
x86_64-Linux (opteron-fc6)

  but fails on ia64-Linux (RH Linux) in flint-1.05 with

  Testing _fmpz_poly_mul_karatsuba()... ok
  Testing _fmpz_poly_mul_karatsuba_trunc()... ok
  Testing _fmpz_poly_mul_karatsuba_trunc_left()... ok
  Testing _fmpz_poly_mul_KS()... GNU MP: Cannot reallocate memory
  (old_size=8 new_size=4294959128)
  ./spkg-check: line 51: 11240 Aborted (core dumped) ./
  fmpz_poly-test

 I found the same bug on an Itanium also with gcc 4.2.2. See

 https://groups.google.com/group/sage-devel/t/a05734c584f012b

 I did run make check on Sage's gmp compiled with that compiler and it
 passes with flying colors. Bill Hart is aware of the problem, but
 currently is still contemplating what would cause this. It looks like
 a potential gmp bug, but so far no one has figured out what is wrong.
 He currently needs access to an actual Itanium to track this down, but
 it looks like William will give him access shortly.

 Another question: I assume we can 
 closehttp://trac.sagemath.org/sage_trac/ticket/1277
 since those two issues you reported there have been resolved. I meant
 to ask for confirmation, but I got side tracked over the last couple
 days :(

  Kate

 Cheers,

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



[sage-devel] implausibly old time stamp in optional package gap_packages-4.4.10_2.spkg

2008-01-09 Thread Kate

When using the optional package 'gap_packages-4.4.10_2.spkg',
if I do

  mv gap_packages-4.4.10_2.spkg  gap_packages-4.4.10_2.tar.bz2
  bunzip2  gap_packages-4.4.10_2.tar.bz2
  tar xf gap_packages-4.4.10_2.tar

then I get

tar: gap_packages-4.4.10_2/src/ctbllib/doc: implausibly old time stamp
1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/tst: implausibly old time stamp
1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/gap4: implausibly old time
stamp 1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/htm: implausibly old time stamp
1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/gap3: implausibly old time
stamp 1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/etc: implausibly old time stamp
1969-12-31 19:00:00
tar: gap_packages-4.4.10_2/src/ctbllib/data: implausibly old time
stamp 1969-12-31 19:00:00

So that this does not worry other people  - it worried me! - perhaps
these
files can be 'touched' and the package rebuilt?

Kate






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



[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

2007-11-08 Thread Kate

Michael,

I have tried

  http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p0.spkg

and can report that it builds on my x86_64-Linux box.  The build is
now
stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for
x86-Linux and ia64-Linux.

Kate


On Nov 7, 6:16 pm, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 On Nov 7, 8:08 pm, William Stein [EMAIL PROTECTED] wrote:



  This should really be sent to sage-devel, so I'm forwarding it there.

  -- Forwarded message --
  From: William Stein [EMAIL PROTECTED]
  Date: Nov 7, 2007 11:07 AM
  Subject: Re: [sage-support] sage-2.8.12 build report
  To: [EMAIL PROTECTED]

  On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote:
   I go away for a while, and now SAGE does not build
   on any of my machines of interest:

   Compiling from source using gcc-4.2.2, I get

   ***
   x86-Linux, ia64-Linux
   ***
   While compiling cvxopt-0.8.2.p4, I get

   gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o
   build/temp.linux-i686-2.5/C/dense.o
   build/temp.linux-i686-2.5/C/sparse.o
   -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib
   -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3
   -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so
   /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95

  That's because you're using gfortran.  Evidently Josh's fix for cvxopt
  not fully working
  fails for people using gfortran.  I'll open a trac ticket:

 http://trac.sagemath.org/sage_trac/ticket/1125

   ***
   x86_64-Linux
   ***
   While compiling libfplll-2.1-20071024, I get

   g++ -shared -nostdlib /usr/lib/../lib64/crti.o
   /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o
.libs/fplll.o  -Wl,--rpath
   -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath
   -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp
   -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2
   -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64
   -L/lib/../lib64 -L/usr/lib/../lib64
   -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib
   -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../..
   /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc
   -lgcc_s 
   /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o
   /usr/lib/../lib64/crtn.o  -Wl,-soname -Wl,libfplll.so.0 -o
   .libs/libfplll.so.0.0.0
   /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation
   R_X86_64_32 against `a local symbol' can not be used when making a
   shared object; recompile with -fPIC
   /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value

   Why is Sage trying to use libmpfr.a out of /usr/lib?  Should it not be
   using the version
   in [sage]/local/lib?

  I agree.  Note that libfpll is a brand new package in Sage (it does
  very fast LLL reduction,
  so is quite important), but it hasn't been as widely tested as other
  components of Sage.
  This is now trac #1126:

 Kate, could you try

 http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p...

 and report back it that solves the issue?

 Cheers,

 Michael



 http://trac.sagemath.org/sage_trac/ticket/1126

  I've made both trac tickets blockers.  We'll fix them at Sage Days next 
  week.

  William

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



[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

2007-11-08 Thread Kate

William,

I am confused about why you forwarded my build report to sage-devel.
According to the About this group

sage-support:  This email list is to report possible bugs in SAGE or
to post a
support-related issue.

sage-devel: This email list is for discussion of SAGE development
issues.

I was trying to build from source - and failed - so that seems to me
to be
more of support issue, rather than a development issue.

If you want, in the future I will send my build problems to sage-
devel.
But if this is really what you want, I recommend that you change the
wording for About this group to more accurately reflect what you
want.

Kate

On Nov 7, 2:08 pm, William Stein [EMAIL PROTECTED] wrote:
 This should really be sent to sage-devel, so I'm forwarding it there.

 -- Forwarded message --
 From: William Stein [EMAIL PROTECTED]
 Date: Nov 7, 2007 11:07 AM
 Subject: Re: [sage-support] sage-2.8.12 build report
 To: [EMAIL PROTECTED]

 On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote:
  I go away for a while, and now SAGE does not build
  on any of my machines of interest:

  Compiling from source using gcc-4.2.2, I get

  ***
  x86-Linux, ia64-Linux
  ***
  While compiling cvxopt-0.8.2.p4, I get

  gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o
  build/temp.linux-i686-2.5/C/dense.o
  build/temp.linux-i686-2.5/C/sparse.o
  -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib
  -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3
  -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so
  /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95

 That's because you're using gfortran.  Evidently Josh's fix for cvxopt
 not fully working
 fails for people using gfortran.  I'll open a trac ticket:

 http://trac.sagemath.org/sage_trac/ticket/1125

  ***
  x86_64-Linux
  ***
  While compiling libfplll-2.1-20071024, I get

  g++ -shared -nostdlib /usr/lib/../lib64/crti.o
  /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o
   .libs/fplll.o  -Wl,--rpath
  -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath
  -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp
  -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2
  -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64
  -L/lib/../lib64 -L/usr/lib/../lib64
  -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib
  -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../..
  /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc
  -lgcc_s 
  /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o
  /usr/lib/../lib64/crtn.o  -Wl,-soname -Wl,libfplll.so.0 -o
  .libs/libfplll.so.0.0.0
  /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation
  R_X86_64_32 against `a local symbol' can not be used when making a
  shared object; recompile with -fPIC
  /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value

  Why is Sage trying to use libmpfr.a out of /usr/lib?  Should it not be
  using the version
  in [sage]/local/lib?

 I agree.  Note that libfpll is a brand new package in Sage (it does
 very fast LLL reduction,
 so is quite important), but it hasn't been as widely tested as other
 components of Sage.
 This is now trac #1126:

http://trac.sagemath.org/sage_trac/ticket/1126

 I've made both trac tickets blockers.  We'll fix them at Sage Days next week.

 William

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



[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report

2007-11-08 Thread Kate

Michael,

Much thanks for the link to Josh's update of cvxopt.spkg.

With that fix, I now can compile on all the architectures
I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux.

The next step is to run 'make check', which I have done.

Sadly, only x86-Linux passes all the tests.

***
x86_64-Linux
***
sage -t  devel/sage-main/sage/rings/real_rqdf.pyx
**
File real_rqdf.pyx, line 12:
sage: RQDF( 123.2) + RR (1.0)
Expected:
124.2000
Got:
NaN
**
File real_rqdf.pyx, line 14:
sage: RQDF( 12.2) + RDF (0.56)
Expected:
12.76
Got:
nan
**
File real_rqdf.pyx, line 16:
sage: RQDF( 12.2) + (9)
Expected:
21.19928945726423989981412887573242187500
Got:
NaN
**

and then others with a similar message: Got NaN or Got nan

***
ia64-Linux
***
The following tests failed:

sage -t  devel/sage-main/sage/lfunctions/lcalc.py
sage -t  devel/sage-main/sage/numerical/test.py
sage -t  devel/sage-main/sage/rings/polynomial/
polynomial_element.pyx

 sage -t  devel/sage-main/sage/lfunctions/lcalc.py
**
File lcalc.py, line 188:
sage: E.Lseries().values_along_line(0.5, 3, 5)
Expected:
lcalc:  1.5 0 WARNING- we don't have enough Dirichlet
coefficients.
lcalc:  Will use the maximum possible, though the output will not
necessarily be accurate.
lcalc:  nan nan
[(0, 0.209951303),
 (0.5, -2...e-16),
 (1., 0.133768433),
 (2., 0.552975867)]
Got:
lcalc:  1.5 0 WARNING- we don't have enough Dirichlet
coefficients.
lcalc:  Will use the maximum possible, though the output will not
necessarily be accurate.
lcalc:  nan nan
[(0, 0.209951303), (0.5, -3.16949699e-16), (1.,
0.133768433), (2., 0.552975867)]
**


sage -t  devel/sage-main/sage/numerical/test.py
**
File test.py, line 4:
: from cvxopt.base import *
Exception raised:
Traceback (most recent call last):
  File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/
doctest.py, line 1212, in __run
compileflags, 1) in test.globs
  File doctest __main__.example_0[0], line 1, in module
from cvxopt.base import *###line 4:
: from cvxopt.base import *
ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe
**

sage -t  devel/sage-main/sage/rings/polynomial/
polynomial_element.pyx**
File polynomial_element.pyx, line 2314:
sage: f.roots(ring=CC)
Expected:
[(1.00, 1), (-0.500 + 0.866025403784438*I,
1), (-0.500 - 0.866025403784438*I, 1)]
Got:
[(1.00, 1), (-0.500 + 0.866025403784439*I,
1), (-0.500 - 0.866025403784439*I, 1)]
**
File polynomial_element.pyx, line 2749:
sage: (x^3 - 1).complex_roots()
Expected:
[1.00, -0.500 + 0.866025403784438*I,
-0.500 - 0.866025403784438*I]
Got:
[1.00, -0.500 + 0.866025403784439*I,
-0.500 - 0.866025403784439*I]
**

Kate

On Nov 8, 10:04 am, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 On Nov 8, 3:59 pm, Kate [EMAIL PROTECTED] wrote:

  Michael,

 Hello Kate,



  I have tried

   http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p...

  and can report that it builds on my x86_64-Linux box.

 Great. I will make sure the updated spkg goes into 2.9 or whatever the
 next release will be.

   The build is
  now
  stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for
  x86-Linux and ia64-Linux.

 Josh did update the cvxopt.spkg (see above in the thread). The latest
 is at

 http://sage.math.washington.edu/home/jkantor/spkgs/cvxopt-0.8.2.p5.spkg

 It should now handle gfortran and g95 without problems. Please report
 back if that solves your problem.

  Kate

 SNIP

 Cheers,

 Michael


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



[sage-devel] Re: sage-2.8.5 on ia64-Linux

2007-09-26 Thread Kate

Bill,

On my ia64-Linux machine,
I get the following error with the -funroll-loops option.  I am
using gcc-4.2.1.  If I take out that option, things compile fine.

make[2]: Entering directory `/home/kate/sage/sage-2.8.5-ia64-Linux/
spkg/build/flint-0.2.p2/src'
gcc -std=c99 -I/usr/include -I/home/kate/sage/sage-2.8.5-ia64-Linux/
local/include/ -I/home/kate/sage/sage-2.8.5-ia64-Linux/local/include  -
funroll-loops -fexpensive-optimizations  -fPIC  -O3 -c ZmodF_mul.c -o
ZmodF_mul.o
In file included from ZmodF.h:19,
 from ZmodF_mul.c:13:
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1600:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1600:
warning: to disable this warning use -fgnu89-inline or the gnu_inline
function attribute
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1626:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1637:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1648:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1659:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1687:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1698:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1711:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1729:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1747:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1758:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1769:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:1779:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:2024:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:2037:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:2050:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:2063:
warning: C99 inline functions are not supported; using GNU89
/home/kate/sage/sage-2.8.5-ia64-Linux/local/include/gmp.h:2076:
warning: C99 inline functions are not supported; using GNU89
ZmodF_mul.c:91: warning: C99 inline functions are not supported; using
GNU89
ZmodF_mul.c:616: warning: C99 inline functions are not supported;
using GNU89
ZmodF_mul.c:695: warning: C99 inline functions are not supported;
using GNU89
ZmodF_mul.c:815: warning: C99 inline functions are not supported;
using GNU89
ZmodF_mul.c:833: warning: C99 inline functions are not supported;
using GNU89
ZmodF_mul.c:857: warning: C99 inline functions are not supported;
using GNU89
ZmodF_mul.c: In function '_ZmodF_mul_fft_convolve_modB2':
ZmodF_mul.c:656: error: unrecognizable insn:
(insn:TI 1048 1533 1038 39 (parallel [
(set (reg:DI 136 f8)
(asm_operands:DI (xma.hu %0 = %2, %3, f0
xma.l %1 = %2, %3, f0) (=f) 0 [
(reg:DI 236 f108 [orig:529 in1_lo ] [529])
(reg:DI 235 f107 [orig:543 in2_lo ] [543])
]
 [
(asm_input:DI (f))
(asm_input:DI (f))
] (ZmodF_mul.c) 617))
(set (reg:DI 137 f9)
(asm_operands:DI (xma.hu %0 = %2, %3, f0
xma.l %1 = %2, %3, f0) (=f) 1 [
(reg:DI 236 f108 [orig:529 in1_lo ] [529])
(reg:DI 235 f107 [orig:543 in2_lo ] [543])
]
 [
(asm_input:DI (f))
(asm_input:DI (f))
] (ZmodF_mul.c) 617))
]) -1 (nil)
(nil))
ZmodF_mul.c:656: internal compiler error: in get_attr_first_insn, at
config/ia64/itanium2.md:1839
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
make[2]: *** [ZmodF_mul.o] Error 1


Kate

On Sep 25, 11:09 am, Bill Hart [EMAIL PROTECTED] wrote:
  On Sep 24, 10:53 pm, Kate Minola [EMAIL PROTECTED] wrote:
   While trying to build sage-2.8.5 on ia64-Linux using
   gcc-4.2.1:

   1.  For flint-0.2.p2, I had to remove the CFLAG
   option

[sage-devel] gmp, mpfr, ecm

2007-09-12 Thread Kate Minola

FYI - the following have recently
been released:

  gmp-4.2.2
  mpfr-2.3.0
  ecm-6.1.3

Kate

-- 
Kate Minola
University of Maryland, College Park

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



[sage-devel] SAGE and ATLAS

2007-07-30 Thread Kate Minola

William,

In the discussion

Problem building linbox on Gentoo Linux (gcc 4.2.0)

you stated:

: There is also http://sagemath.org/SAGEbin/linux/64bit/
: however that binary is not built against ATLAS, whereas if
: you have ATLAS on your system and build SAGE from source
: you'll get a SAGE that is faster at linear algebra.

To get SAGE to build using ATLAS, must ATLAS be installed
in a standard place?  If so, what is that place?  And what version
of ATLAS are you using?

-- 
Kate Minola
University of Maryland, College Park

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



[sage-devel] 2.7.1 and gcc-2.4.1 linbox problem

2007-07-27 Thread Kate Minola

SAGE-2.7.1 sadly does NOT build if you use
the latest stable release of the gcc compiler (gcc-4.2.1).
It fails in linbox for probably the same reason as was
given in the thread:

  2.5.3 and gcc-2.4.0 linbox problem

SAGE-2.7.1 does build and pass its test suite
on my x86-Linux (pentium4) if built with gcc-4.1.2.

-- 
Kate Minola
University of Maryland, College Park

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



[sage-devel] Re: Bug in sage-test (strip_automount_prefix)?

2007-06-05 Thread Kate

Michael,

Which thread?

Kate

On Jun 4, 2:04 pm, Michel [EMAIL PROTECTED] wrote:
 William already posted a patch to this in another thread!

 On Jun 4, 7:39 pm, Nick Alexander [EMAIL PROTECTED] wrote:

   PS. Strictly speaking one should use os.path.separator instead of
   / :-)

  Perhaps os.path.realpath and os.path.normpath are even better?  I
  think Kate Minola will have to patch this, because such automounted
  paths are rare.

  Nick


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



[sage-devel] Re: Bug in sage-test (strip_automount_prefix)?

2007-06-05 Thread Kate

Michael,

Thanks for the URL.  (Alternately, you could have told me to look
in the

maxima.console() works but not maxima.interact()

thread.)

I do not have a problem with William's fix.

To explain why strip_automount_prefix() is necessary, some
computer networks only mount directories on demand.  So for
example, on one network I see

  /u/kate

whereas the absolute path is

  /automount/u/kate

By the way, the word automount could be anything and is
under system administrator control.  So strip_automount_prefix()
just removes this prefix that os.path.abspath() shows.

Nick Alexander suggests using os.path.realpath or os.path.normpath.
Neither work on this network, and so I suspect those functions are
not portable.

Kate

On Jun 5, 9:16 am, Michel [EMAIL PROTECTED] wrote:
 This one!

 Hope the URL works.

 http://groups.google.com/group/sage-devel/browse_thread/thread/ea56d4...

 Michel

 On Jun 5, 2:46 pm, Kate [EMAIL PROTECTED] wrote:

  Michael,

  Which thread?

  Kate

  On Jun 4, 2:04 pm, Michel [EMAIL PROTECTED] wrote:

   William already posted a patch to this in another thread!

   On Jun 4, 7:39 pm, Nick Alexander [EMAIL PROTECTED] wrote:

 PS. Strictly speaking one should use os.path.separator instead of
 / :-)

Perhaps os.path.realpath and os.path.normpath are even better?  I
think Kate Minola will have to patch this, because such automounted
paths are rare.

Nick


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



[sage-devel] Re: Bug in sage-test (strip_automount_prefix)?

2007-06-05 Thread Kate

Michel,

 BTW

 My name is Michel and not Michael!

Sincere apologies!

Kate


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



[sage-devel] 2.5.3 and gcc-2.4.0 linbox problem

2007-05-23 Thread Kate Minola

William,

On my x86-Linux and x86_64-Linux boxes, sage-2.5.3 builds
and successfully passes all tests if built using gcc-4.1.2.

Using the lastest stable release of the gcc compiler suite (gcc-4.2.0),
linbox fails to build.  The first few errors are

g++ -DPACKAGE_NAME=\liblinboxwrap\
-DPACKAGE_TARNAME=\liblinboxwrap\ -DPACKAGE_VERSION=\0.0.1\
-DPACKAGE_STRING=\liblinboxwrap 0.0.1\ -DPACKAGE_BUGREPORT=\\
-DPACKAGE=\liblinboxwrap\ -DVERSION=\0.0.1\ -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_LINBOX_SOLUTIONS_MINPOLY_H=1
-DHAVE_BLAS=1 -I. -I.
-I/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include
-fPIC -I/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include
-L/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/lib -MT
linbox_wrap.lo -MD -MP -MF .deps/linbox_wrap.Tpo -c
src/linbox_wrap.cpp  -fPIC -DPIC -o .libs/linbox_wrap.o
In file included from src/linbox_wrap.cpp:14:
/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include/linbox/algorithms/blas-domain.h:
In member function 'Polynomial
LinBox::BlasMatrixDomainField::charpoly(Polynomial, const Matrix)
const':
/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include/linbox/algorithms/blas-domain.h:443:
error: type/value mismatch at argument 3 in template parameter list
for 'templateclass Field, class Polynomial, templateclass class
Container, class Matrix class LinBox::BlasMatrixDomainCharpoly'
/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include/linbox/algorithms/blas-domain.h:443:
error:   expected a template of type 'templateclass class
Container', got 'templateclass _Tp, class _Alloc class std::list'
/home/kate/sage/sage-2.5.3-x86_64-Linux-pompey/local/include/linbox/algorithms/blas-domain.h:
In member function 'std::listPolynomial, std::allocator_Tp1 
LinBox::BlasMatrixDomainField::charpoly(std::listPolynomial,
std::allocator_Tp1 , const Matrix) const':

I don't have time to investigate further right now. (I am busy
recompiling lots of stuff using gcc-4.2.0.)

---
Kate Minola
University of Maryland, College Park

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



[sage-devel] Re: sage-2.5 build report

2007-05-11 Thread Kate

Yi,

On my ia64-Linux machine I get

% uname -a
Linux lepidus 2.4.21-sgi302r24 #1 SMP Fri Oct 22 22:43:12 PDT 2004
ia64 ia64 ia64 GNU/Linux
% python
Python 2.2.3 (#1, Nov 14 2003, 16:25:37)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)] on linux2
Type help, copyright, credits or license for more information.
 import sys
 sys.platform
'linux2'


Kate


On May 10, 5:56 pm, Yi Qiang [EMAIL PROTECTED] wrote:
 Hi Kate,
 Can you please report what sys.platform says on an ia64 machine?

 On May 10, 2007, at 1:24 PM, Kate Minola wrote:





  William,

  I was able to successfully build sage-2.5 on
  my development network for the following architectures:

 pentium4-Linux
 x86_64-Linux

  Unfortunately when I moved over to a department
  network that uses automounting, the build on
  pentium4-Linux failed in 'linbox' (specifically
  linbox_wrap), and 'make test' failed on x86_64-Linux.
  I have a patch for the the second problem that
  I will send in a separate email.

  On ia64-Linux, 'make test' fails as follows:

  sage.dsage.twisted.tests.test_remote
ClientRemoteCallsTest
  testremoteSubmitBadJob ...
  [OK] testremoteSubmitJob ...
   [OK]
MonitorRemoteCallsTest testget_killed_jobs_list ...
[ERROR]
 [ERROR]
  testremote_get_job ...
   [ERROR]  [ERROR]

  testremote_job_done ...
  [ERROR]
  [ERROR]
  testremote_job_failed ...
  [ERROR]
[ERROR]

  ==
  =
  [ERROR]:
  sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_ki
  lled_jobs_list
  Traceback from remote host -- Traceback unavailable
  ==
  =
  [ERROR]:
  sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_ki
  lled_jobs_list
   Traceback (most recent call last):   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/twisted/pb.py,
  line 420, in requestAvatar
 avatar.attached(avatar, mind)   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/twisted/pb.py,
  line 264, in attached
  self.DSageServer.monitordb.add_monitor(self.host_info)   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/database/monitordb.py,
  line 122, in add_monitor
  cpu_model = host_info['cpu_model'] exceptions.KeyError:
  'cpu_model'

  --
  Kate Minola
  University of Maryland, College Park

 Cheers,
 Yi

 --http://www.yiqiang.net


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



[sage-devel] Re: sage-2.5 build report

2007-05-11 Thread Kate

Yi,

I applied the patch you supplied, but sadly I still get the
same errors.

Kate

On May 11, 11:54 am, Yi Qiang [EMAIL PROTECTED] wrote:
 Hi Kate,
 Can you try applying the follow patch and see if the tests pass now?
 You do not need to run make test all over again, the dsage unit tests
 can be run by simplying typing

 !sage-dsage-trial

 in a SAGE session.

  dsage_hostinfo.patch
 3KDownload



 On May 11, 2007, at 6:05 AM, Kate wrote:





  Yi,

  On my ia64-Linux machine I get

  % uname -a
  Linux lepidus 2.4.21-sgi302r24 #1 SMP Fri Oct 22 22:43:12 PDT 2004
  ia64 ia64 ia64 GNU/Linux
  % python
  Python 2.2.3 (#1, Nov 14 2003, 16:25:37)
  [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)] on linux2
  Type help, copyright, credits or license for more information.
  import sys
  sys.platform
  'linux2'

  Kate

  On May 10, 5:56 pm, Yi Qiang [EMAIL PROTECTED] wrote:
  Hi Kate,
  Can you please report what sys.platform says on an ia64 machine?

  On May 10, 2007, at 1:24 PM, Kate Minola wrote:

  William,

  I was able to successfully build sage-2.5 on
  my development network for the following architectures:

 pentium4-Linux
 x86_64-Linux

  Unfortunately when I moved over to a department
  network that uses automounting, the build on
  pentium4-Linux failed in 'linbox' (specifically
  linbox_wrap), and 'make test' failed on x86_64-Linux.
  I have a patch for the the second problem that
  I will send in a separate email.

  On ia64-Linux, 'make test' fails as follows:

  sage.dsage.twisted.tests.test_remote
ClientRemoteCallsTest
  testremoteSubmitBadJob ...
  [OK] testremoteSubmitJob ...
   [OK]
MonitorRemoteCallsTest testget_killed_jobs_list ...
[ERROR]
 [ERROR]
  testremote_get_job ...
   [ERROR]  [ERROR]

  testremote_job_done ...
  [ERROR]
  [ERROR]
  testremote_job_failed ...
  [ERROR]
[ERROR]

  
  ==
  =
  [ERROR]:
  sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_
  ki
  lled_jobs_list
  Traceback from remote host -- Traceback unavailable
  
  ==
  =
  [ERROR]:
  sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_
  ki
  lled_jobs_list
   Traceback (most recent call last):   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/twisted/pb.py,
  line 420, in requestAvatar
 avatar.attached(avatar, mind)   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/twisted/pb.py,
  line 264, in attached
  self.DSageServer.monitordb.add_monitor(self.host_info)   File
  /home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-
  packages/sage/dsage/database/monitordb.py,
  line 122, in add_monitor
  cpu_model = host_info['cpu_model'] exceptions.KeyError:
  'cpu_model'

  --
  Kate Minola
  University of Maryland, College Park

  Cheers,
  Yi

  --http://www.yiqiang.net

  
 Cheers,
 Yi

 --http://www.yiqiang.net


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



[sage-devel] linbox build problem on pentium4-Linux and work-around

2007-05-11 Thread Kate Minola

I can successfully build sage-2.5 on a pentium4-Linux
running FC6.  Yet on another pentium4-Linux running
RH ELsmp, I get a build failure in linbox.

The problem seems to be missing headers in

 linbox-20070328.p1/linbox_wrap/src/linbox_wrap.cpp

If I add

#include linbox/solutions/rank.h
#include linbox/solutions/det.h

then the build continues successfully.

I do not understand why these missing header files
do  not cause a problem under FC6.

-- 
Kate Minola
University of Maryland, College Park

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



[sage-devel] sage-2.5 build report

2007-05-10 Thread Kate Minola

William,

I was able to successfully build sage-2.5 on
my development network for the following architectures:

   pentium4-Linux
   x86_64-Linux

Unfortunately when I moved over to a department
network that uses automounting, the build on
pentium4-Linux failed in 'linbox' (specifically
linbox_wrap), and 'make test' failed on x86_64-Linux.
I have a patch for the the second problem that
I will send in a separate email.

On ia64-Linux, 'make test' fails as follows:

sage.dsage.twisted.tests.test_remote
  ClientRemoteCallsTest
testremoteSubmitBadJob ...
[OK] testremoteSubmitJob ...
 [OK]
  MonitorRemoteCallsTest testget_killed_jobs_list ...
  [ERROR]
   [ERROR]
testremote_get_job ...
 [ERROR]  [ERROR]
testremote_job_done ... [ERROR]
[ERROR]
testremote_job_failed ...
[ERROR]
  [ERROR]
 ===
[ERROR]: 
sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_killed_jobs_list
Traceback from remote host -- Traceback unavailable
===
[ERROR]: 
sage.dsage.twisted.tests.test_remote.MonitorRemoteCallsTest.testget_killed_jobs_list
 Traceback (most recent call last):   File
/home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-packages/sage/dsage/twisted/pb.py,
line 420, in requestAvatar
avatar.attached(avatar, mind)   File
/home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-packages/sage/dsage/twisted/pb.py,
line 264, in attached
self.DSageServer.monitordb.add_monitor(self.host_info)   File
/home/kate/sage/sage-2.5-ia64-Linux/local/lib/python2.5/site-packages/sage/dsage/database/monitordb.py,
line 122, in add_monitor
cpu_model = host_info['cpu_model'] exceptions.KeyError: 'cpu_model'

-- 
Kate Minola
University of Maryland, College Park

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



[sage-devel] Re: SAGE 2.5 and Cygwin (Status Report)

2007-05-08 Thread Kate

On May 8, 2:02 pm, William Stein [EMAIL PROTECTED] wrote:

 I've posted sage-2.5.rc2 to

http://sage.math.washington.edu/home/was/sage2.5/sage-2.5.rc2.tar

sage-2.5.rc2 fails to build 'matplotlib' with error message

Traceback (most recent call last):
  File setup.py, line 268, in module
build_image(ext_modules, packages, NUMERIX)
  File /home/kate/sage/sage-2.5.rc2-x86-Linux/spkg/build/
matplotlib-0.90.0.p1/setupext.py, line 752, in build_image
add_agg_flags(module)
  File /home/kate/sage/sage-2.5.rc2-x86-Linux/spkg/build/
matplotlib-0.90.0.p1/setupext.py, line 162, in add_agg_flags
add_base_flags(module)
  File /home/kate/sage/sage-2.5.rc2-x86-Linux/spkg/build/
matplotlib-0.90.0.p1/setupext.py, line 138, in add_base_flags
module.library_dirs.extend(libdirs)
AttributeError: 'str' object has no attribute 'extend'
Error building matplotlib package.

I get this build error on both my x86-Linux and my
x86_64-Linux machines.

This did NOT happen with sage-2.5.alpha3 which
build successfully on the same machines.

sage-2.5.alph3: matplotlib-0.90.0
sage-2.5.rc2:matplotlib-0.90.0.p1

Kate Minola
University of Maryland, College Park


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



[sage-devel] Re: sage-2.5.alpha3

2007-05-07 Thread Kate


William,

sage-2.5.alpha3 successfully passes all tests on my x86-Linux and
x86_64-Linux machines.  (I believe this is the first time that sage
has
passed ALL the tests for me.  Yeah!)

It fails the following two tests on my ia64-Linux machine:

 devel/sage-main/sage/plot/plot.py
   *** *** Error: TIMED OUT! *** ***

 devel/sage-main/sage/schemes/elliptic_curves/ell_generic.py

First error message is:

File ell_generic.py, line 220:
sage: eqn = symbolic_expression(E); eqn
Exception raised:
Traceback (most recent call last):
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/docte
st.py, line 1212, in __run
compileflags, 1) in test.globs
  File doctest __main__.example_4[2], line 1, in module
eqn = symbolic_expression(E); eqn###line 220:
sage: eqn = symbolic_expression(E); eqn
  File sage_object.pyx, line 87, in
sage_object.SageObject.__repr__
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/calculus/equations.py, line 114, in _repr_
return %s%s%s %(paren(self._left), symbols[self._op],
paren(self._righ
t))
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/calculus/equations.py, line 70, in paren
return '(%s)'%repr(x)
  File sage_object.pyx, line 87, in
sage_object.SageObject.__repr__
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/calculus/calculus.py, line 2530, in _repr_
return self.simplify()._repr_(simplify=False)
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/calculus/calculus.py, line 1750, in simplify
S =
evaled_symbolic_expression_from_maxima_string(self._maxima_init_())
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/calculus/calculus.py, line 4555, in
evaled_symbolic_expression_fr
om_maxima_string
return symbolic_expression_from_maxima_string(maxima.eval(x))
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/expect.py, line 506, in eval
return '\n'.join([self._eval_line(L) for L in code.split('\n')
if L != '
'])
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/maxima.py, line 531, in _eval_line
self._sendline(line)
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/maxima.py, line 424, in _sendline
self._sendstr(str)
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/maxima.py, line 429, in _sendstr
self._start()
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/maxima.py, line 414, in _start
Expect._start(self)
  File /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/lib/
python2.5/site-
packages/sage/interfaces/expect.py, line 317, in _start
raise RuntimeError, Unable to start %s%self.__name
RuntimeError: Unable to start maxima


When I run /home/kate/sage/sage-2.5.alpha3-ia64-Linux/local/bin/
maxima
I get the maxima startup banner.

Kate Minola
University of Maryland, College Park



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