[sage-devel] Re: C question

2007-06-04 Thread Michel
At the risk of saying something really stupid (as I am relatively clueless in the matter)it seems LD_PRELOAD is often used to achieve the effect you want. Michel On Jun 5, 7:18 am, Joshua Kantor <[EMAIL PROTECTED]> wrote: > This is a C question, I was hoping someone had some advice on. > >

[sage-devel] C question

2007-06-04 Thread Joshua Kantor
This is a C question, I was hoping someone had some advice on. Many linear algebra libraries such as lapack, and blas have an error handling routine called xerbla_ that is called if there is an unrecoverable error. Unfortunately this often calls exit which cannot be caught so sage exits. If one

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

2007-06-04 Thread Michel
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 h

[sage-devel] Re: Sparse Block Diagonal Matrices

2007-06-04 Thread Robert Bradshaw
This is because matrix windows are not matrices--just views into an attached matrix. There is a matrix_from_rows_and_columns command that you might be able to use. sage: M = matrix(QQ, 4, 4, range(16)) sage: M.matrix_from_rows_and_columns([1,2,0],[0,3]) [ 4 7] [ 8 11] [ 0 3] I don't think

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

2007-06-04 Thread Nick Alexander
> 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

[sage-devel] Re: Singular compilation error. File format not recognized??? (Solved(?))

2007-06-04 Thread Michel
I noticed that my jail was missing a find command. I installed it and tried again. This time the compilation worked. I don't see any relation between a missing find command and the error but who knows... gzip, find, flex, bison are some packages that the prerequisite scanner does not check but t

[sage-devel] Re: Singular compilation error. File format not recognized???

2007-06-04 Thread Martin Albrecht
On Monday 04 June 2007 16:39, Michel wrote: > I building SAGE in a FC7 chroot jail in FC4. Everything went fine > until Singular > Singular has problems with ndbm.dl_o. What is ndbm.dl_o??? Maybe a 'make clean' in the Singular and the kernel subdirs helps? -- name: Martin Albrecht _pgp: ht

[sage-devel] Singular compilation error. File format not recognized???

2007-06-04 Thread Michel
I building SAGE in a FC7 chroot jail in FC4. Everything went fine until Singular Singular has problems with ndbm.dl_o. What is ndbm.dl_o??? Michel ==Error message make[3]: Entering directory `/root/sage-2.6/spkg/build/ singular-3-0-2-20070

[sage-devel] Singular compilation error. File format not recognized???

2007-06-04 Thread Michel
I building SAGE in a FC7 chroot jail in FC4. Everything went fine until Singular Singular has problems with ndbm.dl_o. What is ndbm.dl_o??? Michel ==Error message make[3]: Entering directory `/root/sage-2.6/spkg/build/ singular-3-0-2-20070

[sage-devel] Singular compilation error. File format not recognized???

2007-06-04 Thread Michel
I building SAGE in a FC7 chroot jail in FC4. Everything went fine until Singular Singular has problems with ndbm.dl_o. What is ndbm.dl_o??? Michel ==Error message make[3]: Entering directory `/root/sage-2.6/spkg/build/ singular-3-0-2-20070

[sage-devel] Re: sage -upgrade for 2.6

2007-06-04 Thread William Stein
On 6/4/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote: > I'm trying a "sage -upgrade" to go from v. 2.5.3 to 2.6. I'm getting a > patching error on clisp. It wants a "File to patch". Full transcript in the > P.S. Any ideas how I could resolve this? > > I did not try building from scratch using t

[sage-devel] sage -upgrade for 2.6

2007-06-04 Thread Joel B. Mohler
Hi, I'm trying a "sage -upgrade" to go from v. 2.5.3 to 2.6. I'm getting a patching error on clisp. It wants a "File to patch". Full transcript in the P.S. Any ideas how I could resolve this? I did not try building from scratch using the sage-2.6 tarball. I will try that now. -- Joel

[sage-devel] Re: maxima.console() works but not maxima.interact()

2007-06-04 Thread Michel
On Jun 4, 2:46 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Thanks for the bug report about strip_automount_prefix. Please try > the attached sage-test. > > On 6/4/07, Michel <[EMAIL PROTECTED]> wrote: > > > > > > > I am working on my chroot jail but this time I am stuck. Doctests fail > >

[sage-devel] Re: maxima.console() works but not maxima.interact()

2007-06-04 Thread William Stein
On 6/4/07, Michel <[EMAIL PROTECTED]> wrote: > > Does anybody recognize this situation? In particular I am very worried > > that my > > prompt is In [x]: and not sage:... What could possibly cause this? > > > This I could solve by deleting all .directories in the home > directory. > Remains the fa

[sage-devel] Re: maxima.console() works but not maxima.interact()

2007-06-04 Thread Michel
> > Does anybody recognize this situation? In particular I am very worried > that my > prompt is In [x]: and not sage:... What could possibly cause this? > This I could solve by deleting all .directories in the home directory. Remains the fact that interfaces don't start from within sage. Michel

[sage-devel] Re: maxima.console() works but not maxima.interact()

2007-06-04 Thread William Stein
Thanks for the bug report about strip_automount_prefix. Please try the attached sage-test. On 6/4/07, Michel <[EMAIL PROTECTED]> wrote: > > I am working on my chroot jail but this time I am stuck. Doctests fail > because SAGE cannot start the standard interfaces. Here is a typical > exception. >

[sage-devel] Re: GPLv2 or GPLv3?

2007-06-04 Thread William Stein
On 6/4/07, kaimmello <[EMAIL PROTECTED]> wrote: > > Relicensing code is difficult unless you have copyright assignment > > (which SAGE doesn't) or you are a "young" project with contact to all > > (significant) contributers. > > > > If I remember well, somewhere William Stein asked the contributor

[sage-devel] maxima.console() works but not maxima.interact()

2007-06-04 Thread Michel
Hi, I am working on my chroot jail but this time I am stuck. Doctests fail because SAGE cannot start the standard interfaces. Here is a typical exception. In [6]: maxima.interact() --- Traceback (most recent call la

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

2007-06-04 Thread Michel
Hi, I am working on a chroot jail for SAGE under Fedora. I am making good progress and already have a SAGE prompt (a FC7 install inside FC4!). Now I want to run doctests but I am running into a little problem. I have installed SAGE in /sage-2.6.linux32bit-i686-Linux/ (in other words in an immedi

[sage-devel] Re: GPLv2 or GPLv3?

2007-06-04 Thread kaimmello
> Relicensing code is difficult unless you have copyright assignment > (which SAGE doesn't) or you are a "young" project with contact to all > (significant) contributers. > If I remember well, somewhere William Stein asked the contributors to put him as a co-owner of the copyright, it was to sol

[sage-devel] Re: GPLv2 or GPLv3?

2007-06-04 Thread mabshoff
On Jun 4, 11:21 am, kaimmello <[EMAIL PROTECTED]> wrote: > On Jun 4, 11:03 am, Michel <[EMAIL PROTECTED]> wrote: > > > Personally I think the extra patent protection provided by the GPL3 > > would be a good thing for SAGE and for open source CAS's in general. > > I agree with you because algorit

[sage-devel] Re: GPLv2 or GPLv3?

2007-06-04 Thread kaimmello
On Jun 4, 11:03 am, Michel <[EMAIL PROTECTED]> wrote: > Personally I think the extra patent protection provided by the GPL3 > would be a good thing for SAGE and for open source CAS's in general. I agree with you because algorithms of CAS's can be patented in the future and GPLv3 protects againt

[sage-devel] Re: GPLv2 or GPLv3?

2007-06-04 Thread Michel
Personally I think the extra patent protection provided by the GPL3 would be a good thing for SAGE and for open source CAS's in general. But I assume this issue depends mainly on the software SAGE itself depends on. I might be mistaken but I think Maxima is GPL2 only. Michel PS. I think the GPL3

[sage-devel] GPLv2 or GPLv3?

2007-06-04 Thread kaimmello
The last draft of GPLv3 has been released. Richard Stallman himself has said that GPLv2 and GPLv3 are incompatible, i.e. you can't merge code with this two licenses. I was wondering what SAGE will do about this. Will it remain GPLv2? Or will it become GPLv3? Personally I hope the second. Regards