[sage-devel] Re: sage+gap conf stuff

2007-09-16 Thread William Stein

On 9/16/07, David Joyner [EMAIL PROTECTED] wrote:
 Some comments on the recent GAP comments relevant to SAGE:

 (0) The talk on SAGE went quite well and generated interest.

Excellent.

 (1) Many GAP developers and some GAP packages authors like
 SAGE and plan on looking into the extra functionality of GAP-SAGE
 (ie, the GAP that comes with SAGE). Especially the HAP team.
 I would like to include HAP as standard as soon as we can.
 (There still is a documented HAP function which returns a list sometimes
 and an integer others. I have them 2 ways to remedy this which are
 fairly easy. Once they fix this, i would like it to be included.
 Further HAP development will use polymake, which is already a
 SAGE package.)

Just get it to work for me easily and I'll include it.

 (2) Many really liked the SAGE gui. Unfortunately, the TUB (Tech Univ at
 Braunschweig) wirefall blocked the online authentication so it could not
 be used and there was no internet at the hotel.

For future reference, about 3-4 days ago I changed things so that the
public notebook server:
   (1) Doesn't use ssl at all, and
   (2) Is at http://sagenb.org  (and another at http://sagenb.com), so
 there is no funny business with ports.
Thus the above setup shouldn't get blocked anywhere anymore.
Obviously (1) means people could sniff password on the public notebook
easily, but this really isn't too worrisome given that the thing is free,
etc., so what should people expect?

 (3) The Browse package authors (which used ncurses to do some fancy
 display tricks with large character tables, for example) wished that it
 could be used in the gui. I have no idea if you can pipe ncurses
 special characters through to the browser and make it look nicer.

I have no clue if that is possible or if it would be a good idea. Probably not.

 In general, for SAGE's browser, how do you view a section of a huge
 (say character or Cayley) table? They have solved this problem using Browse,
 which leaves the side and top alone (which index the rows and columns)
 but allows you to browse 5 or 10 consecutive rows and column entries.

I suspect HTML and any good web browser solves this problem ok -- just
make aread-only textarea or span or div tag with a limited number of
rows and columns, and the browser provides good scroll functionality.  This
is one thing that browsers are surprisingly good at.

 (4) Single processor machines are almost a thing of the past.
 How do we start to adjust for this increase in processors?

DSAGE, IPython1, multithreaded BLAS, etc.

 Can SAGE use a single GAP workspace but start two (or more)
 threads using that?

I don't know what that means, due to my lack of knowledge about
GAP.

  Which basic commands (like polynomial
 multiplication) can be parallelized?

For atomic operations like that, most anything can be parallelized.
The amusing thing is that usually the overhead of starting threads
and keeping track of them ends up making the resulting code
slower than not using threads at all.   In my opinion the *only* reason
to ever use parallelism is to make things faster -- period.  If
a parallel implementation isn't demonstrably faster than a serial
one, then there is no point (though there are some issues of scaling).

In numerous cases basic arithmetic, linear algebra, etc. in SAGE / GAP
is way slower than Magma's serial implementations, so in such cases
one should at least catch up with (or beat) them first.   Finally, in many
cases Sage's basic arithmetic is done by third-party libraries,
in order to avoid us reinventing the wheel... our multivariate polynomial
arithmetic is often done by Singular -- and it would probably takes
years of hard work to come up with our own serial multivariate polynomial
arithmetic that would beat Singular (note that Singular actually beats
Magma in many cases). And then once we understand our serial
implementation, we have to do something parallel that is even better.

So I think nontrivial parallelization at the low-level arithmetic level is not
something that is going to happen soon, except if any third party
libraries were to do it.   One exception is linear algebra, where SAGE
uses Linbox, which in turn using a system-wide optimized BLAS -- and
one can get optimized BLAS's that really do leverage multicore machines,
e.g., this is standard on OS X.  So already much of SAGE's linear algebra
benefits from multicore machines, without us doing any work to make
that happen.

Parallelization at a higher level, e.g., dsage, ipython1, etc., is of course
very important and is currently being used all the time by people.

 (5) How easy would it be to certify a computation? Suppose
 f is a function, x is input and y is output and I claim GAP (or SAGE)
 tells me that, after several days, y = f(x). I want you to believe me,
 so I certify this. One way (maybe) is to have SAGE encrypt the
 start time, finish time, and printout (and maybe a pickle of some
 relevant data) into a file. This file looks random 

[sage-devel] Re: sage+gap conf stuff

2007-09-16 Thread Mike Hansen

Speaking of parallel processing in Python, I recently heard about the
pp module:
http://www.parallelpython.com/  It may be something that we want to look at.

--Mike

On 9/16/07, William Stein [EMAIL PROTECTED] wrote:

 On 9/16/07, David Joyner [EMAIL PROTECTED] wrote:
  Some comments on the recent GAP comments relevant to SAGE:
 
  (0) The talk on SAGE went quite well and generated interest.

 Excellent.

  (1) Many GAP developers and some GAP packages authors like
  SAGE and plan on looking into the extra functionality of GAP-SAGE
  (ie, the GAP that comes with SAGE). Especially the HAP team.
  I would like to include HAP as standard as soon as we can.
  (There still is a documented HAP function which returns a list sometimes
  and an integer others. I have them 2 ways to remedy this which are
  fairly easy. Once they fix this, i would like it to be included.
  Further HAP development will use polymake, which is already a
  SAGE package.)

 Just get it to work for me easily and I'll include it.

  (2) Many really liked the SAGE gui. Unfortunately, the TUB (Tech Univ at
  Braunschweig) wirefall blocked the online authentication so it could not
  be used and there was no internet at the hotel.

 For future reference, about 3-4 days ago I changed things so that the
 public notebook server:
(1) Doesn't use ssl at all, and
(2) Is at http://sagenb.org  (and another at http://sagenb.com), so
  there is no funny business with ports.
 Thus the above setup shouldn't get blocked anywhere anymore.
 Obviously (1) means people could sniff password on the public notebook
 easily, but this really isn't too worrisome given that the thing is free,
 etc., so what should people expect?

  (3) The Browse package authors (which used ncurses to do some fancy
  display tricks with large character tables, for example) wished that it
  could be used in the gui. I have no idea if you can pipe ncurses
  special characters through to the browser and make it look nicer.

 I have no clue if that is possible or if it would be a good idea. Probably 
 not.

  In general, for SAGE's browser, how do you view a section of a huge
  (say character or Cayley) table? They have solved this problem using Browse,
  which leaves the side and top alone (which index the rows and columns)
  but allows you to browse 5 or 10 consecutive rows and column entries.

 I suspect HTML and any good web browser solves this problem ok -- just
 make aread-only textarea or span or div tag with a limited number of
 rows and columns, and the browser provides good scroll functionality.  This
 is one thing that browsers are surprisingly good at.

  (4) Single processor machines are almost a thing of the past.
  How do we start to adjust for this increase in processors?

 DSAGE, IPython1, multithreaded BLAS, etc.

  Can SAGE use a single GAP workspace but start two (or more)
  threads using that?

 I don't know what that means, due to my lack of knowledge about
 GAP.

   Which basic commands (like polynomial
  multiplication) can be parallelized?

 For atomic operations like that, most anything can be parallelized.
 The amusing thing is that usually the overhead of starting threads
 and keeping track of them ends up making the resulting code
 slower than not using threads at all.   In my opinion the *only* reason
 to ever use parallelism is to make things faster -- period.  If
 a parallel implementation isn't demonstrably faster than a serial
 one, then there is no point (though there are some issues of scaling).

 In numerous cases basic arithmetic, linear algebra, etc. in SAGE / GAP
 is way slower than Magma's serial implementations, so in such cases
 one should at least catch up with (or beat) them first.   Finally, in many
 cases Sage's basic arithmetic is done by third-party libraries,
 in order to avoid us reinventing the wheel... our multivariate polynomial
 arithmetic is often done by Singular -- and it would probably takes
 years of hard work to come up with our own serial multivariate polynomial
 arithmetic that would beat Singular (note that Singular actually beats
 Magma in many cases). And then once we understand our serial
 implementation, we have to do something parallel that is even better.

 So I think nontrivial parallelization at the low-level arithmetic level is not
 something that is going to happen soon, except if any third party
 libraries were to do it.   One exception is linear algebra, where SAGE
 uses Linbox, which in turn using a system-wide optimized BLAS -- and
 one can get optimized BLAS's that really do leverage multicore machines,
 e.g., this is standard on OS X.  So already much of SAGE's linear algebra
 benefits from multicore machines, without us doing any work to make
 that happen.

 Parallelization at a higher level, e.g., dsage, ipython1, etc., is of course
 very important and is currently being used all the time by people.

  (5) How easy would it be to certify a computation? Suppose
  f is a function, x is input 

[sage-devel] Re: Sage 2.8.3 on Solaris - A New Hope

2007-09-16 Thread didier deshommes

2007/9/16, mabshoff [EMAIL PROTECTED]:
 Solaris 10 on Opteron:

 toolchain:

 ../gcc-4.2.1/configure --with-ld=/usr/sfw/i386-sun-solaris2.10/bin/ld
 --with-as=/usr/sfw/bin/gas \
 --prefix=/usr/local/gcc-4.2.1 --enable-languages=c,c++,fortran --with-
 gmp=/usr/local/gmp-4.2.2-32/ \
 --with-mpfr=/usr/local/mpfr-2.2.1p2-32/
 ###
 Issues:
 ###

I am using solaris 10 also (granted, on a p4), but so far I'm not
running into as many issues are you are:
~/custom/sage-2.8.4.2 $ uname -a
SunOS unknown 5.11 snv_57 i86pc i386
~/custom/sage-2.8.4.2 $ gcc -v
Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
Target: i386-pc-solaris2.8
Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
--with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
--enable-shared --enable-multilib --enable-nls --with-included-gettext
--with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
--with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
Thread model: posix
gcc version 4.0.2

I am using  pre-compiled packages from blastwave. The only showstopper
has been lapack:
sage_fortran -fPIC  -c lsame.f -o lsame.o
ld.so.1: f951: fatal: relocation error: file
/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.0.2/f951: symbol
__gmpn_clz_tab: referenced symbol not found

ntl, python, libgcrypt and even linbox are some of the packages that
build flawlessly.

didier


 * libgcrypt-1.2.4

 In src/tests/Makefile.in:

 LINK = $(LIBTOOL) --tag=CC --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS)
 \
 $(AM_LDFLAGS) $(LDFLAGS) -lnsl -lsocket -lmp -lscf -lgen -
 ldoor -lmd -lgcc_s -L/lib/ -luutil -o $@

 Bug in os installation: in /lib: missing link to libuutil.so from
 libuutil.so.1?

 * opencdk-0.5.9

 In src/tests/Makefile.in:

 LINK = $(LIBTOOL) --tag=CC --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS)
 \
 $(AM_LDFLAGS) $(LDFLAGS) \
 -lnsl -lsocket -lmp -lscf -lgen -ldoor -lmd -lgcc_s -L/lib/ -
 luutil -o $@


 * gnutls-1.6.3: unresolved problem:

 /bin/bash ../libtool --tag=CC   --mode=link gcc  -D_REENTRANT -
 D_THREAD_SAFE -Wno-pointer-sign -pipe -I/export/home/mabshoff/
 sage-2.8.4.2/local/include  -I/export/home/mabshoff/sage-2.8.4.2/local/
 include   -lnsl -lsocket -lmp -lscf -lgen -ldoor -lmd -lgcc_s -L/lib/ -
 luutil -o gnutls-serv serv-gaa.o serv.o common.o select.o ../lib/
 libgnutls.la ../libextra/libgnutls-extra.la -L/export/home/mabshoff/
 sage-2.8.4.2/local/lib -lgcrypt -L/export/home/mabshoff/sage-2.8.4.2/
 local/lib -lgpg-error
 gcc -D_REENTRANT -D_THREAD_SAFE -Wno-pointer-sign -pipe -I/export/home/
 mabshoff/sage-2.8.4.2/local/include -I/export/home/mabshoff/
 sage-2.8.4.2/local/include -o .libs/gnutls-serv serv-gaa.o serv.o
 common.o select.o  -lnsl -lsocket -lmp -lscf -lgen -ldoor -lmd -lgcc_s
 -L/lib/ -luutil ../lib/.libs/libgnutls.so -L/export/home/mabshoff/
 sage-2.8.4.2/local/lib ../libextra/.libs/libgnutls-extra.so /export/
 home/mabshoff/sage-2.8.4.2/spkg/build/gnutls-1.6.3/src/lib/.libs/
 libgnutls.so -lz -lxnet /export/home/mabshoff/sage-2.8.4.2/local/lib/
 libgcrypt.so /export/home/mabshoff/sage-2.8.4.2/local/lib/libgpg-
 error.so -Wl,--rpath -Wl,/export/home/mabshoff/sage-2.8.4.2/local/lib
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'
 ../libextra/.libs/libgnutls-extra.so: undefined reference to
 [EMAIL PROTECTED]'

 Odd, because ntohs and so on are in -lsocket -lnls -lresovl - cc
 shooting across. Sun ld issue?

 * python: needs -lrt -laio -lmd for symbols sem_init() - bug in
 configure script.
   -lmd also fixes md5 import problem.

   problems with sockets - see below:

 * twisted: import socket fails

 running install_egg_info
 Writing /export/home/mabshoff/sage-2.8.4.2/local/lib/python2.5/site-
 packages/zope.interface-3.3.0-py2.5.egg-info
 Traceback (most recent call last):
   File setup.py, line 20, in module
 from twisted import copyright
   File ./twisted/__init__.py, line 26, in module
 from twisted.python import compat
   File ./twisted/python/compat.py, line 15, in module
 import sys, string, socket, struct
   File /export/home/mabshoff/sage-2.8.4.2/local/lib/python2.5/
 socket.py, line 45, in module
 import _socket
 ImportError: No module named _socket
 Error: Subprocess exited with result 1 for project core
 Error installing Twisted networking 

[sage-devel] Re: Sage 2.8.3 on Solaris - A New Hope

2007-09-16 Thread mabshoff



On Sep 16, 8:17 pm, didier deshommes [EMAIL PROTECTED] wrote:
 2007/9/16, mabshoff [EMAIL PROTECTED]:

  Solaris 10 on Opteron:

  toolchain:

  ../gcc-4.2.1/configure --with-ld=/usr/sfw/i386-sun-solaris2.10/bin/ld
  --with-as=/usr/sfw/bin/gas \
  --prefix=/usr/local/gcc-4.2.1 --enable-languages=c,c++,fortran --with-
  gmp=/usr/local/gmp-4.2.2-32/ \
  --with-mpfr=/usr/local/mpfr-2.2.1p2-32/
  ###
  Issues:
  ###

Hello Didier,


 I am using solaris 10 also (granted, on a p4), but so far I'm not
 running into as many issues are you are:
 ~/custom/sage-2.8.4.2 $ uname -a
 SunOS unknown 5.11 snv_57 i86pc i386

it looks like you are running a fairly recent OpenSolaris build. But
is it pure OpenSolaris or Nexenta? I know you used Nexenta in the
past, but that is quite different because the userspace is close to
100% GNU while Solaris is sufficiently different to cause issues. I
run the latest official Solaris 10 U4:

uname -a
SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc

 ~/custom/sage-2.8.4.2 $ gcc -v
 Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
 Target: i386-pc-solaris2.8
 Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
 --with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
 --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
 --enable-shared --enable-multilib --enable-nls --with-included-gettext
 --with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
 --with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
 Thread model: posix
 gcc version 4.0.2

 I am using  pre-compiled packages from blastwave.

 --enable-threads=posix might take care of some of the python issue.
I have seen python 2.5.1 at blastwave.org, so I assume it is possible
to build it without too much fiddling. William and  I wanted to build
everything from source without the need to install external packages.
And we are trying to also get it to work in Solaris 9.

 The only showstopper  has been lapack:
 sage_fortran -fPIC  -c lsame.f -o lsame.o
 ld.so.1: f951: fatal: relocation error: file
 /opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.0.2/f951: symbol
 __gmpn_clz_tab: referenced symbol not found

Haven't seen that one. But it is a GMP symbol and I have no idea why
that would be linked against Lapack. The BlastWave binary also seems
to have been compiled for Solaris 2.8, so that might be an issue.


 ntl, python, libgcrypt and even linbox are some of the packages that
 build flawlessly.

No real surprises expect for Python. I assumed that that was one of
the packages that would just build. I regularly build LinBox on
Solaris, so in any other case let me know. I had to patch lcalc, but
that fix is going in soon.


 didier

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.3 on Solaris - A New Hope

2007-09-16 Thread didier deshommes

2007/9/16, mabshoff [EMAIL PROTECTED]:
 it looks like you are running a fairly recent OpenSolaris build. But
 is it pure OpenSolaris or Nexenta? I know you used Nexenta in the
 past, but that is quite different because the userspace is close to
 100% GNU while Solaris is sufficiently different to cause issues. I
 run the latest official Solaris 10 U4:

It is pure Solaris. More specifically this is Solaris Express
Community Edition b57. The only modifications I made is that I  use
gnu build tools whenever I can (ie gmake, gcc, gas, ranlib, tar, etc).
I hope that answers your question.


 uname -a
 SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc

  ~/custom/sage-2.8.4.2 $ gcc -v
  Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
  Target: i386-pc-solaris2.8
  Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
  --with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
  --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
  --enable-shared --enable-multilib --enable-nls --with-included-gettext
  --with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
  --with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
  Thread model: posix
  gcc version 4.0.2
 
  I am using  pre-compiled packages from blastwave.

  --enable-threads=posix might take care of some of the python issue.
 I have seen python 2.5.1 at blastwave.org, so I assume it is possible
 to build it without too much fiddling. William and  I wanted to build
 everything from source without the need to install external packages.
 And we are trying to also get it to work in Solaris 9.


 Haven't seen that one. But it is a GMP symbol and I have no idea why
 that would be linked against Lapack. The BlastWave binary also seems
 to have been compiled for Solaris 2.8, so that might be an issue.

Come to thinks about it, I think the gfortran lapack package installs
mpfr (or gmp I can't remember) with it. The solution might as simple
as grabbing the gfortran binary for x86-solaris and installing it
manually.

didier

 


--~--~-~--~~~---~--~~
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.3 on Solaris - A New Hope

2007-09-16 Thread mabshoff

On Sep 16, 9:13 pm, didier deshommes [EMAIL PROTECTED] wrote:
 2007/9/16, mabshoff [EMAIL PROTECTED]:

Hello Didier,


  it looks like you are running a fairly recent OpenSolaris build. But
  is it pure OpenSolaris or Nexenta? I know you used Nexenta in the
  past, but that is quite different because the userspace is close to
  100% GNU while Solaris is sufficiently different to cause issues. I
  run the latest official Solaris 10 U4:

 It is pure Solaris. More specifically this is Solaris Express
 Community Edition b57. The only modifications I made is that I  use
 gnu build tools whenever I can (ie gmake, gcc, gas, ranlib, tar, etc).
 I hope that answers your question.


Pretty much. I saw that you ran the nevada kernel and build 57. I
never ran Nexenta, but now found out that its uname does mention it
and the blaswave packages do not run on it. But Solaris Express seems
to be a lot more current than Solaris 10, just look at the difference
between Solaris 9 and 10 to get an idea many problems just vanish
between those two releases.

Regarding the GNU tools: I installed those from the official Solaris
10 DVD and then build my own environment. I am curious if my issues
will go away with Solaris Express, but I still need to be able to
build on 9  10. For example: the math department at Dortmund they
still runs Solaris 9 on all Sparc hardware and there are no plans to
introduce 10, much less run Solaris Express. Only recently the Solaris
8 boxen were upgraded, so Solaris installations have a tendency to
stick around quite some time (which shouldn't come as a surprise to
anybody who ever worked on/with Solaris - if it ain't broken, don't
fix it)

I don't think we should support Sage in Solaris/x86 on anything older
but 10, but for Sparc support for 9 would be good.


  uname -a
  SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc

   ~/custom/sage-2.8.4.2 $ gcc -v
   Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
   Target: i386-pc-solaris2.8
   Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
   --with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
   --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
   --enable-shared --enable-multilib --enable-nls --with-included-gettext
   --with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
   --with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
   Thread model: posix
   gcc version 4.0.2

   I am using  pre-compiled packages from blastwave.

   --enable-threads=posix might take care of some of the python issue.
  I have seen python 2.5.1 at blastwave.org, so I assume it is possible
  to build it without too much fiddling. William and  I wanted to build
  everything from source without the need to install external packages.
  And we are trying to also get it to work in Solaris 9.

  Haven't seen that one. But it is a GMP symbol and I have no idea why
  that would be linked against Lapack. The BlastWave binary also seems
  to have been compiled for Solaris 2.8, so that might be an issue.

 Come to thinks about it, I think the gfortran lapack package installs
 mpfr (or gmp I can't remember) with it. The solution might as simple
 as grabbing the gfortran binary for x86-solaris and installing it
 manually.


Sounds like the solution. I really dislike the fact that pkgadd cannot
deal with dependencies properly. But it is common practice to
statically link gmp  mpfr against any gcc compiler, 4.2. actually
warns you about dynamic libraries if I recall correctly.

 didier



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+gap conf stuff

2007-09-16 Thread Martin Albrecht

 For future reference, about 3-4 days ago I changed things so that the
 public notebook server:
(1) Doesn't use ssl at all, and
(2) Is at http://sagenb.org  (and another at http://sagenb.com), so
  there is no funny business with ports.
 Thus the above setup shouldn't get blocked anywhere anymore.
 Obviously (1) means people could sniff password on the public notebook
 easily, but this really isn't too worrisome given that the thing is free,
 etc., so what should people expect?

Did SSL slow down the machines that were running the public notebook? Did you 
run into scalability problems? If there is one lesson to be learned from 
it-sec than it is: people are amazingly stupid when it comes to it-sec. If 
you want to demonstrate that with SAGE you can easily work over the network 
using just a webbrowser (i.e. fullfill the promises of the webapps buzz) it 
is -- at least to me -- a requirement to not gamble with a user's 
credentials. Using a non-encrypted login page is -- again, at least to me -- 
a gamble with the user's credential. To sum up: I strongly vote for 
re-enabling SSL encryption.

Martin


-- 
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=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/
-~--~~~~--~~--~--~---



[sage-devel] Re: Sage 2.8.3 on Solaris - A New Hope

2007-09-16 Thread [EMAIL PROTECTED]

I just wanted to say awesome and keep up the good work.  I'll be
testing Sage on Solaris/x86 soon.

On Sep 16, 3:25 pm, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
 On Sep 16, 9:13 pm, didier deshommes [EMAIL PROTECTED] wrote:

  2007/9/16, mabshoff [EMAIL PROTECTED]:

 Hello Didier,



   it looks like you are running a fairly recent OpenSolaris build. But
   is it pure OpenSolaris or Nexenta? I know you used Nexenta in the
   past, but that is quite different because the userspace is close to
   100% GNU while Solaris is sufficiently different to cause issues. I
   run the latest official Solaris 10 U4:

  It is pure Solaris. More specifically this is Solaris Express
  Community Edition b57. The only modifications I made is that I  use
  gnu build tools whenever I can (ie gmake, gcc, gas, ranlib, tar, etc).
  I hope that answers your question.

 Pretty much. I saw that you ran the nevada kernel and build 57. I
 never ran Nexenta, but now found out that its uname does mention it
 and the blaswave packages do not run on it. But Solaris Express seems
 to be a lot more current than Solaris 10, just look at the difference
 between Solaris 9 and 10 to get an idea many problems just vanish
 between those two releases.

 Regarding the GNU tools: I installed those from the official Solaris
 10 DVD and then build my own environment. I am curious if my issues
 will go away with Solaris Express, but I still need to be able to
 build on 9  10. For example: the math department at Dortmund they
 still runs Solaris 9 on all Sparc hardware and there are no plans to
 introduce 10, much less run Solaris Express. Only recently the Solaris
 8 boxen were upgraded, so Solaris installations have a tendency to
 stick around quite some time (which shouldn't come as a surprise to
 anybody who ever worked on/with Solaris - if it ain't broken, don't
 fix it)

 I don't think we should support Sage in Solaris/x86 on anything older
 but 10, but for Sparc support for 9 would be good.





   uname -a
   SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc

~/custom/sage-2.8.4.2 $ gcc -v
Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
Target: i386-pc-solaris2.8
Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
--with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
--enable-shared --enable-multilib --enable-nls --with-included-gettext
--with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
--with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
Thread model: posix
gcc version 4.0.2

I am using  pre-compiled packages from blastwave.

--enable-threads=posix might take care of some of the python issue.
   I have seen python 2.5.1 at blastwave.org, so I assume it is possible
   to build it without too much fiddling. William and  I wanted to build
   everything from source without the need to install external packages.
   And we are trying to also get it to work in Solaris 9.

   Haven't seen that one. But it is a GMP symbol and I have no idea why
   that would be linked against Lapack. The BlastWave binary also seems
   to have been compiled for Solaris 2.8, so that might be an issue.

  Come to thinks about it, I think the gfortran lapack package installs
  mpfr (or gmp I can't remember) with it. The solution might as simple
  as grabbing the gfortran binary for x86-solaris and installing it
  manually.

 Sounds like the solution. I really dislike the fact that pkgadd cannot
 deal with dependencies properly. But it is common practice to
 statically link gmp  mpfr against any gcc compiler, 4.2. actually
 warns you about dynamic libraries if I recall correctly.

  didier

 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.3 on Solaris - A New Hope

2007-09-16 Thread mabshoff



On Sep 17, 12:16 am, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 I just wanted to say awesome and keep up the good work.  I'll be
 testing Sage on Solaris/x86 soon.


Well, we are getting very close now:

Hangs (due to pecpect issues?):

sage -t  rings/polynomial/multi_polynomial_element.py
sage -t  rings/polynomial/toy_buchberger.py

Total list of failures:

sage -t  calculus/calculus.py
sage -t  functions/constants.py
sage -t  functions/piecewise.py
sage -t  functions/special.py
sage -t  functions/transcendental.py
sage -t  interfaces/maxima.py
sage -t  interfaces/singular.py
sage -t  lfunctions/sympow.py
sage -t  matrix/matrix_integer_dense.pyx
sage -t  matrix/matrix_space.py
sage -t  modular/ssmod/ssmod.py
sage -t  rings/polynomial/multi_polynomial_element.py
sage -t  rings/polynomial/multi_polynomial_ring_generic.pyx
sage -t  rings/polynomial/toy_buchberger.py
sage -t  rings/complex_double.pyx
sage -t  rings/power_series_ring.py
sage -t  rings/real_double.pyx
sage -t  schemes/elliptic_curves/ell_rational_field.py

Last missing piece of software: sympow, most of the failures are
caused by a couple bugs, most of the doctests are due to numerical
noise, nan vs. NaN and some other small issues. The rng also behaves
differently. I opened tickets #667-#676 and hopefully we will get them
fixed during Bug Day 3 this Thursday.

Didier, does sage -testall pass on your install?

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: Interactive cells, GUIs, javascript, ...

2007-09-16 Thread Chris Chiasson

One last thing, I wanted to say that my earlier Mathematica comments
do not (usually) apply when dealing with the individual developers,
who are (usually) very helpful, especially on MathGroup. The thing I
am complaining about is the overall process of reporting and fixing
problems.

On Sep 14, 5:50 pm, Chris Chiasson [EMAIL PROTECTED] wrote:
 ... wait until you actually start pushing Mathematica, it gets
 sluggish on you, produces wrong results and/or crashes, and you
 receive apathy and blame dodging instead of tech support and bug
 fixing.

 On Sep 14, 3:31 pm, Hamptonio [EMAIL PROTECTED] wrote:

  Recently I started using Mathematica 6 in the computer labs of some
  courses I teach, and I cannot help but be impressed.  The new dynamic
  commands such as Manipulate are very impressive, and are perfect for
  teaching.  Before seeing how powerful it is, I had hoped to switch
  from using mathematica to sage in the fall of 2008.  But now I am not
  sure I can justisfy that switch or convince my colleagues it would
  make sense.  (As an aside: assume for the sake of argument that my
  department gets mathematica for free, which is true in a certain
  bureaucratic sense).

  For some sense of what mathematica can now do, check 
  out:http://www.wolfram.com/products/mathematica/newin6/content/DynamicInt
  I actually think its more impressive in person.

  While I would like to help remedy the gap between sage and mathematica/
  matlab in this respect, I am not sure how it would be done.  I am
  learning a little about wxPython, but I don't think that would work
  through the notebook at all, unless a program was created on the
  server for download and byte-compilation by the client.  Does anyone
  have any ideas? If javascript is a possibility, can someone recommend
  a good reference for learning to use it for such complicated
  purposes?  Or is java an option?

  -Marshall


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