[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-27 Thread Martin Albrecht
Hi David, I am working through my todo list and thus revisited this thread. Right now, I am not sure what I can do to help you to fix the problems you identified (due to lack of knowledge about the platforms in question) On the other hand, I am very interested in making M4RI truly

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-27 Thread Dr David Kirkby
On Oct 27, 11:34 am, Martin Albrecht m...@informatik.uni-bremen.de wrote: Hi David, I am working through my todo list and thus revisited this thread. Right now, I am not sure what I can do to help you to fix the problems you identified (due to lack of knowledge about  the platforms in

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-27 Thread Martin Albrecht
I think the test for cach size and number of CPUs should be removed from the configure script, for several reasons. From what I can gather from the autoconf list * Both macros, which you took from the auotconf macro archive, are badly written - not just in what they do, but in a very

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-27 Thread David Kirkby
2009/10/27 Martin Albrecht m...@informatik.uni-bremen.de: I tend to agree with your point when it comes to the number of CPUs, that probably should be run-time instead of compile time. Btw. I just checked, this information isn't even used! This is now:

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-14 Thread Martin Albrecht
On Wednesday 14 October 2009, Dr. David Kirkby wrote: libm4ri has two issues that I am aware of as soon as one tries to use a non-GNU or non-86 environment. I believe the developers hang out here, so I'll put a bit of information here, on the hope they see it. 1) Despite the fact Sun's

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-14 Thread Dr. David Kirkby
Martin Albrecht wrote: On Wednesday 14 October 2009, Dr. David Kirkby wrote: libm4ri has two issues that I am aware of as soon as one tries to use a non-GNU or non-86 environment. I believe the developers hang out here, so I'll put a bit of information here, on the hope they see it. 1)

[sage-devel] Re: libm4ri issues with non-GNU/x86 environments.

2009-10-14 Thread Martin Albrecht
2) On HP-UX, the configure script can't work out how many CPUs I have, what sort they are, but then tries to determine the cache size. This causes the configure script to break. The macro for determining the number of CPUs

[sage-devel] Re: libm4ri thinks the Sun C compiler is broken

2009-09-27 Thread Dr. David Kirkby
Dr. David Kirkby wrote: Using * Solaris 10 update 7 on SPARC * sage-4.1.2.alpha2 * Sun Studio 12.1 * An updated configure script to allow the Sun compiler to be used http://sagetrac.org/sage_trac/ticket/7021 CC was set to the Sun C compiler. Despite thousands of

[sage-devel] Re: libm4ri

2008-12-02 Thread Martin Albrecht
I plan to upgrade png in 3.2.2 and will also attempt to do the upgrade to fplll 3.0.x. I guess if malb is ok with the rename we could also change the name next time he releases an updated version. I named it libm4ri because this naming scheme is consistent with what Debian does (usually

[sage-devel] Re: libm4ri

2008-12-01 Thread mabshoff
On Dec 1, 8:40 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: I just noticed for m4ri the package is called libm4ri-*.spkg. Any   reason this isn't m4ri-*.spkg? That is the name malb gave it initially and it just stuck. The same applies for libfplll.spkg, too. - Robert Cheers, Michael

[sage-devel] Re: libm4ri

2008-12-01 Thread Robert Bradshaw
On Dec 1, 2008, at 8:42 PM, mabshoff wrote: On Dec 1, 8:40 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: I just noticed for m4ri the package is called libm4ri-*.spkg. Any reason this isn't m4ri-*.spkg? That is the name malb gave it initially and it just stuck. The same applies for

[sage-devel] Re: libm4ri

2008-12-01 Thread mabshoff
On Dec 1, 8:51 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Dec 1, 2008, at 8:42 PM, mabshoff wrote: On Dec 1, 8:40 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: I just noticed for m4ri the package is called libm4ri-*.spkg. Any reason this isn't m4ri-*.spkg? That is the name malb

[sage-devel] Re: libm4ri

2008-12-01 Thread Robert Bradshaw
On Dec 1, 2008, at 8:54 PM, mabshoff wrote: On Dec 1, 8:51 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Dec 1, 2008, at 8:42 PM, mabshoff wrote: On Dec 1, 8:40 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: I just noticed for m4ri the package is called libm4ri-*.spkg. Any reason this

[sage-devel] Re: libm4ri

2008-12-01 Thread mabshoff
On Dec 1, 9:11 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Dec 1, 2008, at 8:54 PM, mabshoff wrote: On Dec 1, 8:51 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: On Dec 1, 2008, at 8:42 PM, mabshoff wrote: On Dec 1, 8:40 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: I just