linbox-devel Google Group

Re: LinBox 1.1.6 and debianization

tabb...@mit.edu (Timothy G Abbott) — Sat, 14 Jun 2008 20:34:41 UT

Probably the right thing to do is put in doc/ (or a new directory man/)
and add code to Makefile.am to install it as $mandir/man1/linbox-config.1.
I think the automake way to do this is to add to Makefile.am
man1_MANS = linbox-config.1
You'll probably want to set linbox-config.1 to be automatically

LinBox 1.1.6 and debianization

clement.per...@gmail.com (Clement Pernet) — Sat, 14 Jun 2008 19:50:02 UT

Hi all,
The linbox 1.1.6 release candidate #0 is almost ready:
* I shaved out the gmp++ of LinBox, and made Givaro a mandatory package,
so that LinBox uses Givaro gmp++
* Merged in the sage wrapper in the interface directory
* Fixed the remaining gcc-4.3 warnings.
* fixed other bugs
Tim, I just need you to tell me what should I do with the man page

Re: [linbox-devel] Re: [debian-sage] Linbox in Debian

clement.per...@gmail.com (Clement Pernet) — Wed, 11 Jun 2008 17:28:20 UT

Hi,
This gmp++ conflict is the last step before releasing 1.1.6 and the
debianization.
Dave suggested to get rid of the linbox gmp++ and only use givaro's
gmp++ thus making givaro a mandatory package for linbox.
Does anyone object to this decision?
If not, we are going to do it these coming days.
patch is now obsolete due to recent changes upstream.

Release 1.1.6

clement.per...@gmail.com (Clement Pernet) — Wed, 04 Jun 2008 20:28:42 UT

Hi LinBoxers,
If you missed it, Tim Abbott presented in this thread
[link]
the work he did for packaging LinBox as a debian package. This was done
in the process of packaging Sage in debian.
As I answered in this thread, I will work on fixing the last issues left

Re: [debian-sage] Linbox in Debian

michael.absh...@mathematik.uni-dortmund.de (mabshoff) — Tue, 27 May 2008 19:01:48 UT

Hi,

Yep, that is actually a situation that might happen and leave some
people rather surprised that uninstalling Linbox breaks Givaro.

No objections from the Sage side of things ;)

<SNIP>

FYI: We currently have the following patch applied to the Sage
Linbox.spkg

[link]

Re: [linbox-devel] Re: [debian-sage] Linbox in Debian

saund...@udel.edu (David Saunders) — Tue, 27 May 2008 18:28:30 UT

We should clean up this gmp++ business in a way that makes it easy for
givaro and linbox to UNinstall cleanly. I suppose it could be "last one
out the door, take gmp++ with you." In other words linbox's uninstall
should look for the presence of givaro and uninstall gmp++ only if
givaro is not there. This is not very satisfactory and it is easy to

Re: [debian-sage] Linbox in Debian

clement.per...@gmail.com (Clement Pernet) — Tue, 27 May 2008 18:10:30 UT

Hi,
First, thank you Tim (and Michael) for the work you've done on porting
into Debian.
This issue was raised several times by Mabshoff, and the only diff I get
from the 2 versions is in gmp++.h, whith the different defines of Givaro
and LinBox.
I am going to uniformize it, but as was mentionned in the later

Re: [linbox-devel] Re: proposal for FieldAXPY change of interface

clement.per...@gmail.com (Clement Pernet) — Tue, 27 May 2008 17:49:49 UT

Hi,
I agree with idea of giving the field interface to FieldAXPY.
Now, J-G, you say LasyField could inherit from both Field and FieldAXPY.
I don't see the need for it, since FieldAXPY already inherited from Field.
Is there a specific reason why LasyField should be different from
FiedlAXPY? Instead, we could, just have a single class, LazyField,

Linbox in Debian (fwd)

tabb...@mit.edu (Timothy G Abbott) — Mon, 26 May 2008 00:00:41 UT

I'm resending this email because it hasn't made it into the linbox-devel
archives. I'm not sure what went wrong here; perhaps it is that I also
sent it to debian-sage@googlegroups.com.
-Tim Abbott
---------- Forwarded message ----------
Reply-To: debian-sage@googlegroups.com
To: linbox-devel@googlegroups.com

Linbox in Debian

tabb...@mit.edu (Timothy G Abbott) — Sun, 25 May 2008 03:44:36 UT

I've been working on getting SAGE into Debian, and as part of this project,
I've packaged LinBox for Debian. My goal is to get LinBox and SAGE into the
Debian lenny release, which will be frozen in 4 or 5 weeks (so ideally the
package should be ready in 2-3 weeks).
I have a draft package for LinBox available in the repository described at

Re: [linbox-devel] proposal for FieldAXPY change of interface

saund...@udel.edu (B.David Saunders) — Sun, 25 May 2008 13:49:02 UT

Jean-Guillaume, I like your idea very much.
FieldAXPY has proved it's worth and is ready to be "mainstreamed".
I recommend the version where the unnormalized values live in a type declared in
the lazy field,
rather than using values wrapped in a FieldAXPY object. One reason for this is
to mainstream the

proposal for FieldAXPY change of interface

jean-guillaume.du...@imag.fr (Jean-Guillaume Dumas) — Thu, 22 May 2008 09:27:03 UT

Currently the FieldAXPY objects stores a field and an element.
This is a lot of storage for a single scalar element.
I would rather see the FieldAXPY object be more like a field object, i.e.
leave the element to be a parameter of the FieldAXPY methods e.g. :
inline Element& accumulate (Element& _y, const Element &t)

Re: LinBox v2.0 design

saund...@udel.edu (David Saunders) — Thu, 10 Apr 2008 22:03:02 UT

Clement, Thanks for setting up this framework for 2.0 design
discussion.

I agree that proposals can be made both by mods to the wiki pages (a
collaborative/competitive design process that wikis are good for). and
by initial discussion here. I'll try some of each.

(1) I added some functions to the blackbox list on the matrixDesign

Re: [linbox-devel] Hadamard bound computation and mpfr

saund...@udel.edu (David Saunders) — Mon, 10 Mar 2008 13:04:12 UT

It seems to me this dependency lies within the GMP dependency we have,
so I don't see any problem with use of mpfr.
-dave
PS. Since it is a bound, I would think the mantissa accuracy of double
is sufficient. But when the exponent is exceeded, well, then you need
realer real numbers!

LinBox v2.0 design

clement.per...@gmail.com (Clement Pernet) — Sat, 08 Mar 2008 00:08:16 UT

Hi folks,
Let's start working on the design for LinBox version 2.0.
First, I could not find the wiki page that was written after our Post
ISSAC07 discussions.
The page [link] now points
to the irrelevant page
[link].