[sage-devel] problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[Francois]

Hi all,

I have trouble compiling sage on my linux box which is as follow:
x86 (amd athlon - definitely not amd64)
distro is gentoo up to date as of last week. kernel 2.6.23, glibc
2.6.1
gcc-4.2.2, binutils-2.18.
The problem I have is in the compilation of sage itself more precisely
libcsage.

Here is the last message:
sage: Building and installing modified SAGE library files.


Installing c_lib
gcc -o src/convert.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include
-I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/python2.5 -I/
home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -Iinclude
src/convert.c
gcc -o
src/interrupt.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/interrupt.c
gcc -o
src/mpn_pylong.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/mpn_pylong.c
gcc -o
src/mpz_pylong.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/mpz_pylong.c
gcc -o
src/stdsage.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/stdsage.c
gcc -o
src/gmp_globals.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/gmp_globals.c
g++ -o
src/ZZ_pylong.os -c -fPIC -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/
python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -
Iinclude
src/ZZ_pylong.cpp
g++ -o
src/ntl_wrap.os -c -fPIC -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/
python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -
Iinclude
src/ntl_wrap.cpp
ld -o libcsage.so -shared -no_archive src/convert.os src/interrupt.os
src/mpn_pylong.os src/mpz_pylong.os src/stdsage.os src/gmp_globals.os
src/ZZ_pylong.os
src/ntl_wrap.os -L/home/francois/Work/Gentoo/sage-2.9.1.1/local/lib -
lntl -lgmp -lpari
ld: cannot find -lpari
scons: *** [libcsage.so] Error 1



I poked around a bit and the problem is not with pari. The problem
is the parameter "-no_archive". My version of ld from binutils-2.18
doesn't
support such an option. In fact if it did, it should be --no_archive
as it is
the option can be interpreted as -n -o _archive and if I try to issue
it
again I end up with a file called _archive and a message about
creating an
archive containing DT_TEXTREL symbols.

Removing the -no_archive gives a normal result. Unfortunately I don't
know how
to resume the compilation process correctly from there as scons behave
very
differently from make.

I don't where to patch things so that it doesn't happen in the first
place. I
cannot find anything about this parameter in the SConstruct file or
spkg-install. I don't know where to look from there.

Things did go normally with sage 2.8.12 the first I compiled, I first
had the
problem trying to compile 2.8.15 and ever since. I didn't try 2.8.13.
or .14.

Any idea?

Cheers from New Zealand,
Francois

--~--~-~--~~~---~--~~
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: problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[mabshoff]

On Dec 28, 9:47 am, Francois <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have trouble compiling sage on my linux box which is as follow:
> x86 (amd athlon - definitely not amd64)
> distro is gentoo up to date as of last week. kernel 2.6.23, glibc
> 2.6.1
> gcc-4.2.2, binutils-2.18.
> The problem I have is in the compilation of sage itself more precisely
> libcsage.
>
> Here is the last message:
> sage: Building and installing modified SAGE library files.
>


>
> I poked around a bit and the problem is not with pari. The problem
> is the parameter "-no_archive". My version of ld from binutils-2.18
> doesn't
> support such an option. In fact if it did, it should be --no_archive
> as it is
> the option can be interpreted as -n -o _archive and if I try to issue
> it
> again I end up with a file called _archive and a message about
> creating an
> archive containing DT_TEXTREL symbols.
>
> Removing the -no_archive gives a normal result. Unfortunately I don't
> know how
> to resume the compilation process correctly from there as scons behave
> very
> differently from make.
>
> I don't where to patch things so that it doesn't happen in the first
> place. I
> cannot find anything about this parameter in the SConstruct file or
> spkg-install. I don't know where to look from there.

cd into devel/sage and execute "sage -b". That should continue the
build process.

> Things did go normally with sage 2.8.12 the first I compiled, I first
> had the
> problem trying to compile 2.8.15 and ever since. I didn't try 2.8.13.
> or .14.
>
> Any idea?

Thanks for the report. I will be looking into this.

> Cheers from New Zealand,
> Francois

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: Most Sage spkg's are out of date!

[Ondrej Certik]

On Dec 27, 2007 1:55 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > What *standard* Sage spkg packages are out of date right now
> > (I'm skimminghttp://sagemath.org/components.html)?
> >
> >  * cddlib: we ship 094b, but 094d is current.
> >  * clisp: we ship clisp-2.41, but  2.43 is current  (I'm sure you can 
> > comment!)
> >  * cvxopt: we ship 0.9 but 0.9.1 is out.  It has "efficient Python
> > classes for dense and sparse matrices (real and complex), with Python
> > indexing and slicing and overloaded operations for matrix arithmetic"
> > -- looks cool!
> >  * gd: we ship 2.0.33 but 2.0.36 is current
> >  * gfan: we ship 0.2.2 but 0.3 is current
> >  * givaro: we ship 3.2.6 but 3.2.9 is current
> >  * gmp: we ship 4.2.1 but 4.2.2 is current
> >  * gnutls: we ship 1.6.3 but 2.2.0 is current!
> >  * gsl: we ship 1.9 but 1.10 is current
> >  * jsmath: I don't even know what we ship (it's at most 3.4d), but
> > current is 3.4f
> >  * iml: we ship 1.0.1, but 1.0.2 is current (I think 1.0.2 is
> > upstreaming our changes
> > in a way that breaks things for us...)
> >  * ipython: we ship 0.8.1, but 0.8.2 is current
> >  * lcalc: we ship 20070107, but 20070902 is current.
> >  * libgcrypt: ???
>
> Current release is 1.4.0 which is available from http://www.gnupg.org/
> - the old site at the FSF seems to have stopped updating. I have been
> wrestling with building the current libgcrypt.spkg for a while on
> Cygwin now and it seems impossible to build a shared version, which
> causes no end of troubles for GNUTLS.
>
> Cheers,
>
> Michael
>
>
> >  * Maxima: we ship 5.13, but 5.14 is current.
> >  * Moinmoin: we ship 1.5.7 but 1.5.8 is current
> >  * numpy: we ship 1.0.3 but 1.0.4 is current
> >  * opencdk: we ship 0.5.9 but 0.6.6 is current
> >  * pari: we ship 2.3.2 but 2.3.3 is current (I posted a new spkg tonight)
> >  * pexpect: we ship 2.0 but 2.3 is current (2.1 sucked (!); maybe 2.3 is 
> > good??)
> >  * lippng: we ship 1.2.22, but 1.2.24 is current
> >  * quaddouble: we ship 2.2, but 2.3.1 is current
> >  * sqlite: we ship 3.5.3 but 3.5.4 is current
> >  * sympy: we ship 0.5.7 but 0.5.9 is current
> >  * zodb: we ship 3.7.0 but 3.7.2 is current
> >
> > So about half the spkg's in Sage are out of date right now.
> >
> > What should we do?   Any ideas?  People who work on Linux distributions,
> > please speak up, except for saying "don't bother with Sage, we already
> > package everything above in Debian" -- keep in mind Sage also targets OS X
> > and Solaris.
> >
> > A possible solution might include:
> >
> >(1) Find somebody to volunteer for a while to be the "package
> > version maiden"
> >  sort of like how Michael Abshoff has been the "trac maiden".
> >  This person
> >  would keep track of a list like the above, possibly only a
> > wiki, or possible
> >  right in trac.  For each package, if we aren't upgrading
> > there has to be a clear
> >  reason why.
> >(2) Get 2 volunteers to maintain each of the above packages (2
> > instead of 1 to
> >  improve continuity and fill in gaps).   Basically
> >  there are already very hard working package maintainers for
> > about half the
> >  packages in Sage; this list above is the other half.
> >(3) Referee spkg updates.
> >
> > If you're one of the people that lobbied hard for inclusion of a
> > package in Sage,
> > you might consider volunteering to officially maintain it.
> >
> > It's obviously not the end of the world if some of the spkg's in sage 
> > aren't the
> > latest versions -- some projects release new versions very often.  But many
> > of the projects listed above release a new version maybe once every 6 
> > months,
> > so we really need to find a way to get on top of things.   That said, there 
> > are
> > often major and difficult integration issues when putting new versions of
> > packages in Sage, e.g., updating matplotlib recently caused a lot of pain.
> > So we don't want to do things too quickly.


Are there some instructions for Sage package maintainers to follow?
I.e. what exact steps are neede to update the package?

1) create a new spkg
2) create a trac ticket and attach it? or expose the repository, so
that you can build it yourself?
3) write to the mailinglist?

Ondrej

--~--~-~--~~~---~--~~
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" google pagerank

[Ondrej Certik]

On Dec 26, 2007 4:45 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Right now in the US if you search for "sage" in Google then
> sagemath.org comes up first.Finally!

So now Sage finally started to live, when people can actually find it.

But I like it, picking a name that was hopelessly buried in google search
results and then slowly beating all other "sage"s until sagemath is fist,
good job! :)

Ondrej

--~--~-~--~~~---~--~~
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" google pagerank

[Harald Schilly]

very nice! Do you track the referring page for search-keywords? Would
be very interesting to know for what people are really searching for
when hitting the sage page.

H
--~--~-~--~~~---~--~~
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: cremona package under Sage

[bill.p]

Here's a plea to whoever last maintained the mwrank-python (why do I
always type pythin?) interface:
Please can you explain to me how it fits together? I can follow the
Python so far but cannot see how
the arguments get passed between the Python bits and the C++ code.
What is that bit of C++
in .../sage/libs/mwrank ? Does Python do a dynamic link every time the
package is invoked?

Thanks in advance,

Bill
--~--~-~--~~~---~--~~
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.9.2

[Harald Schilly]

On Dec 28, 7:56 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> html(' width="800" height="650"
> codebase="http://sage.math.washington.edu/home/tkosan/mathrider/";
> archive="mathrider.jar" MAYSCRIPT>
>

Hi, above code didn't work, but inserting it in "Edit" mode did the
trick. Well, looks nice, but is just related, not really what i was
thinking about. If I manage to put together an example of my idea I'll
tell you.

Harald
--~--~-~--~~~---~--~~
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] GUI widgets in the notebook (was sage-2.9.2)

[Ted Kosan]

Harald wrote:

> Have you thought more generally about interactive cells? A widget
> included in the answer-cell, which assignes values to a local variable
> and then issues an update for reevaluation.
> I've just written feature request #1613
> http://sagetrac.org/sage_trac/ticket/1613
>
> ...
>
> On Dec 28, 7:56 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> > html(' > width="800" height="650"
> > codebase="http://sage.math.washington.edu/home/tkosan/mathrider/";
> > archive="mathrider.jar" MAYSCRIPT>
> >
>
> Hi, above code didn't work, but inserting it in "Edit" mode did the
> trick. Well, looks nice, but is just related, not really what i was
> thinking about. If I manage to put together an example of my idea I'll
> tell you.

I looked into this and discovered that the reason the code did not
work is because it had carriage returns placed into it by the email
system :-)


I think I know something of what you are thinking about.  Here are a
couple more applets you can try to see if I am getting closer to your
vision (just remove all carriage returns except the one at the end
before executing this code in a notebook cell):


This applet demonstrates a bunch of GUI widgets that can be placed
into the notebook:

html('http://sage.math.washington.edu/home/tkosan/mathrider/SwingSet";
archive="SwingSet.jar" MAYSCRIPT>')


And this one demonstrates dynamic 2D graphics that can be run in the notebook:

html('http://sage.math.washington.edu/home/tkosan/mathrider/Java2D/";
archive="Java2Demo.jar" MAYSCRIPT>')

Ted

--~--~-~--~~~---~--~~
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: problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[mabshoff]

On Dec 28, 9:47 am, Francois <[EMAIL PROTECTED]> wrote:
> Hi all,
>


Hello Francois,

> I poked around a bit and the problem is not with pari. The problem
> is the parameter "-no_archive". My version of ld from binutils-2.18
> doesn't
> support such an option. In fact if it did, it should be --no_archive
> as it is
> the option can be interpreted as -n -o _archive and if I try to issue
> it
> again I end up with a file called _archive and a message about
> creating an
> archive containing DT_TEXTREL symbols.
>
> Removing the -no_archive gives a normal result. Unfortunately I don't
> know how
> to resume the compilation process correctly from there as scons behave
> very
> differently from make.
>
> I don't where to patch things so that it doesn't happen in the first
> place. I
> cannot find anything about this parameter in the SConstruct file or
> spkg-install. I don't know where to look from there.
>
> Things did go normally with sage 2.8.12 the first I compiled, I first
> had the
> problem trying to compile 2.8.15 and ever since. I didn't try 2.8.13.
> or .14.
>
> Any idea?

I did poke around and there is no place in Sage that sets that flag.
Even a grep -r over a complete from source install does not yield any
hits. Since we import the current ENV into SCons is there any chance
it is in your ENV?

> Cheers from New Zealand,
> Francois

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.9.2

[William Stein]

On Dec 27, 2007 4:51 PM, Harald Schilly <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 27, 9:37 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > ... interactive 3d graphics
>
> > What do you think?
>
> Have you thought more generally about interactive cells? A widget
> included in the answer-cell, which assignes values to a local variable
> and then issues an update for reevaluation.
> I've just written feature request #1613
> http://sagetrac.org/sage_trac/ticket/1613

OK, how about the following as the main goals for 3.0, which
we should aim for completing by Feb 21, 2008 say (my
birthday):

 (1) SOLARIS: Full Solaris 10 support on Opteron and Sparc,

 (2) 3D: Excellent interactive 3d graphics from the notebook
   and command line.

 (3) DEMOS: A demos server with interactive web-based use of Sage
   for specific applications, along with a catalogue of 500
   examples that illustrate Sage and drive traffice to sagemath.org

(4) DOCTESTS: Raise the doctest coverage of the Sage library at 50%.
  (Right now it is at 35.5%).


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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] Re: problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[Francois]

Hello Michael,

I think I found my problem. A little googling actually helped with
this link:
http://bugs.archlinux.org/task/6864
I did some experiments with the intel _fortran_ compiler (not even the
C compiler)
and I still have it on my system.
Since the intel compiler doesn't compile my lattice QCD code correctly
anyway
I will remove it and try again.
I am busy for the next few hours so I will do that a bit latter.

Thanks for looking,
Francois
--~--~-~--~~~---~--~~
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: Most Sage spkg's are out of date!

[William Stein]

On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Are there some instructions for Sage package maintainers to follow?
> I.e. what exact steps are neede to update the package?

There are no instructions, and no master list of package maintainers, etc.
One of the goals of this thread is to create such things.

> 1) create a new spkg
> 2) create a trac ticket and attach it? or expose the repository, so
> that you can build it yourself?
> 3) write to the mailinglist?

We need:
  (a)  a wiki page that lists packages with the corresponding maintainer.
  (b) A natural system for updating patches.  I like your suggestion above,
though _not_ the order.
  (1) Create a trac ticket describing that the package is out of date.
This should _already_ be done for every package I listed at
 the beginning of this email.
  (2) Accept the trac ticket when you're about to make a new spkg.
  (3) Post a link from the trac ticket to the new spkg (don't
attach it, since
it is too big.)
  (4) Post to sage-devel announcing the new spkg and requesting
feedback and testing.  Any such email *must* list some tests
a user can try after "sage -i" 'ing the package to test that
it actually installed OK.  All feedback from such testing
should be pasted into the trac ticket.  The trac ticket should
be assigned against an upcoming release of Sage.
 (5)  The release manager puts the new spkg in Sage once it
has got a positive review as a part of (4).

Thoughts?

 -- 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] Re: Fwd: About SAGE

[William Stein]

On Dec 27, 2007 5:58 AM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Dec 27, 2007 3:40 AM, William Stein <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I occasionally get emails like the one below.  There's no way I have the
> > time or inclination to burn and mail out DVD's of Sage to people.  Does
> > anybody:
> >
> >(1) want to volunteer to do this sort of thing in exchange for some
> >  "shipping and handling fees"; then all such requests get
> >  refereed to you, or
> >
> >(2) Is there some dot-com that does something like this for a fee?
>
>
>
>
> Maybe lulu does:
> http://www.lulu.com/en/help/disc_faq
> Apparently, It has to be set up first and I don't know how easy it is to
> upgrade to a new version.

This looks excellent.   Basically you upload an iso of the data dvd, and
they burn and ship it on demand for < $10/copy.This is perfect.  I could
just do this once every time we have a major release.   I can add a few
dollars on each DVD, to pay whoever actually does the work of putting
together the ISO, updating it, etc.

David -- many thanks for tracking this down.

 -- 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] Rosetta translations

[TimDaly]

At  is a document that is
designed
to help users of new systems "translate" simple ideas from their
current systems.
(The source is at ). I do
not know
Sage well enough to update this information. Is there anyone here who
can
propose Sage equivalent commands so they can be added to the document?
It should only take a few minutes for an experienced Sage user.

Please send me email or post an updated version of the document
somewhere.

Such a translation would be a trivial introduction to Sage and could
be added
to the distribution.

Tim Daly


--~--~-~--~~~---~--~~
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: [Axiom-developer] Rosetta translations

[David Joyner]

I think this is a great idea.

What distribution license does the rosetta tex file have?


On 12/28/07, TimDaly <[EMAIL PROTECTED]> wrote:
> At  is a document that is
> designed
> to help users of new systems "translate" simple ideas from their
> current systems.
> (The source is at ). I do
> not know
> Sage well enough to update this information. Is there anyone here who
> can
> propose Sage equivalent commands so they can be added to the document?
> It should only take a few minutes for an experienced Sage user.
>
> Please send me email or post an updated version of the document
> somewhere.
>
> Such a translation would be a trivial introduction to Sage and could
> be added
> to the distribution.
>
> Tim Daly
>
>
>
> ___
> Axiom-developer mailing list
> [EMAIL PROTECTED]
> http://lists.nongnu.org/mailman/listinfo/axiom-developer
>

--~--~-~--~~~---~--~~
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: About SAGE

[Robert Bradshaw]

On Dec 28, 2007, at 1:06 PM, William Stein wrote:

> On Dec 27, 2007 5:58 AM, David Joyner <[EMAIL PROTECTED]> wrote:
>>
>> On Dec 27, 2007 3:40 AM, William Stein <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> I occasionally get emails like the one below.  There's no way I  
>>> have the
>>> time or inclination to burn and mail out DVD's of Sage to  
>>> people.  Does
>>> anybody:
>>>
>>>(1) want to volunteer to do this sort of thing in exchange for  
>>> some
>>>  "shipping and handling fees"; then all such requests get
>>>  refereed to you, or
>>>
>>>(2) Is there some dot-com that does something like this for a  
>>> fee?
>>
>>
>>
>>
>> Maybe lulu does:
>> http://www.lulu.com/en/help/disc_faq
>> Apparently, It has to be set up first and I don't know how easy it  
>> is to
>> upgrade to a new version.
>
> This looks excellent.   Basically you upload an iso of the data  
> dvd, and
> they burn and ship it on demand for < $10/copy.This is  
> perfect.  I could
> just do this once every time we have a major release.   I can add a  
> few
> dollars on each DVD, to pay whoever actually does the work of putting
> together the ISO, updating it, etc.
>
> David -- many thanks for tracking this down.

This does look perfect. Once this is set up, creating and uploading  
the iso should be a trivial task (done via a script), and if the  
artwork remained the same for all double-point releases that should  
be easy too, so I don't think a couple of dollars is worth the hassle  
of collecting and re-distributing it. I'll volunteer to set it up  
(though until 2.9.2 I'm going to be focusing on the 3d stuff).

- Robert


--~--~-~--~~~---~--~~
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: [Axiom-developer] Rosetta translations

[root]

>I think this is a great idea.
>
>What distribution license does the rosetta tex file have?

Modified BSD.

I'd like Sage to be in the list so people from other systems
can have a clue what form they might type in Sage to get
similar results.

Tim

--~--~-~--~~~---~--~~
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: [Jmol-developers] [sage-devel] Re: Jmol and Mathematics Visualization

[Robert Bradshaw]

On Dec 28, 2007, at 11:20 AM, Miguel wrote:

>>> I suspect that you will encounter other issues with lighting on
>>> very flat
>>> triangles and "cracking" in triangulated surfaces. As I  
>>> understand it,
>>> these are typical problems with graphics engines ... and there was
>>> never
>>> much demand for these kinds of things within Jmol.
>>
>> Java3D seems to handle this kind of thing fine, so I'm sure it can be
>> done with Jmol too (just that no one's needed/noticed it before).
>
> Agreed.

Any ideas?

>> I was thinking about implementing a "binary" pmesh (same exact
>> format), unless someone's already done that. Also, it'd be nice to
>> read in a whole bundle of files at once (I'm thinking a .zip file
>> with a script and all associated resources).
>
> I think that would be fine.
>
> Jmol has support built in for gzip files. Any molecular data file  
> format
> can be gzipped and Jmol will automagically unzip it.
>
> gzip was nicer for this application because I was reading a single  
> file.

Yes. I think the binary -> decimal -> binary conversion eats up a lot  
of overhead though (at least on our side it's a the bulk of the time).

> zip (jar) would be better for sets of files ... although Jmol  
> currently
> doesn't have any mechanism to deal with a directory of files. That  
> is, it
> wouldn't know which of the files you wanted to *open* and what you  
> would
> want to do with the other files.

There'd be a designated script file, and it would just use the load  
command to load other files in that same zip archive.

- Robert



--~--~-~--~~~---~--~~
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: Most Sage spkg's are out of date!

[David Joyner]

On Dec 28, 2007 2:38 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Are there some instructions for Sage package maintainers to follow?
> > I.e. what exact steps are neede to update the package?
>
> There are no instructions, and no master list of package maintainers, etc.
> One of the goals of this thread is to create such things.
>
> > 1) create a new spkg
> > 2) create a trac ticket and attach it? or expose the repository, so
> > that you can build it yourself?
> > 3) write to the mailinglist?
>
> We need:
>   (a)  a wiki page that lists packages with the corresponding maintainer.

I've created

http://wiki.sagemath.org/standard_packages_available_for_SAGE

http://wiki.sagemath.org/optional_packages_available_for_SAGE

http://wiki.sagemath.org/experimental_packages_available_for_SAGE

The information on these pages varies but I think all items need  work.


>   (b) A natural system for updating patches.  I like your suggestion above,
> though _not_ the order.
>   (1) Create a trac ticket describing that the package is out of date.
> This should _already_ be done for every package I listed at
>  the beginning of this email.
>   (2) Accept the trac ticket when you're about to make a new spkg.
>   (3) Post a link from the trac ticket to the new spkg (don't
> attach it, since
> it is too big.)
>   (4) Post to sage-devel announcing the new spkg and requesting
> feedback and testing.  Any such email *must* list some tests
> a user can try after "sage -i" 'ing the package to test that
> it actually installed OK.  All feedback from such testing
> should be pasted into the trac ticket.  The trac ticket should
> be assigned against an upcoming release of Sage.
>  (5)  The release manager puts the new spkg in Sage once it
> has got a positive review as a part of (4).
>
> Thoughts?
>
>  -- 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] Re: Most Sage spkg's are out of date!

[Ted Kosan]

William wrote:

> What should we do?   Any ideas?  People who work on Linux distributions,
> please speak up, except for saying "don't bother with Sage, we already
> package everything above in Debian"

Since Gentoo is a meta Linux distribution (a distribution which is
designed to build custom distributions) it contains the tools needed
to automate package management and creation including: source code
fetching, patching, dependencies, compiler configuration, package
maintainer coordination, etc.  It also has tools which automatically
create CD and DVD images.

It might be less effort overall to construct SAGE's package creation
system and overall build system on top of something like Gentoo than
to do it manually and coordinate everything with trac/wiki.

Ted

--~--~-~--~~~---~--~~
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: problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[mabshoff]

On Dec 28, 8:36 pm, Francois <[EMAIL PROTECTED]> wrote:
> Hello Michael,

Hello Francois,

> I think I found my problem. A little googling actually helped with
> this link:http://bugs.archlinux.org/task/6864
> I did some experiments with the intel _fortran_ compiler (not even the
> C compiler)
> and I still have it on my system.
> Since the intel compiler doesn't compile my lattice QCD code correctly
> anyway
> I will remove it and try again.
> I am busy for the next few hours so I will do that a bit latter.

This is actually something we can prevent on our end by forcing SCons
to use the GNU compilers instead of the Intel ones in case they are
present. I had to fix similar issues on Solaris when Sun's compilers
were installed and SCons picked those over gcc. Thanks for tracking
this down. This is now

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

> Thanks for looking,
> Francois

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: Most Sage spkg's are out of date!

[mabshoff]

On Dec 29, 4:52 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> William wrote:
> > What should we do?   Any ideas?  People who work on Linux distributions,
> > please speak up, except for saying "don't bother with Sage, we already
> > package everything above in Debian"
>
> Since Gentoo is a meta Linux distribution (a distribution which is
> designed to build custom distributions) it contains the tools needed
> to automate package management and creation including: source code
> fetching, patching, dependencies, compiler configuration, package
> maintainer coordination, etc.  It also has tools which automatically
> create CD and DVD images.
>
> It might be less effort overall to construct SAGE's package creation
> system and overall build system on top of something like Gentoo than
> to do it manually and coordinate everything with trac/wiki.

Well, if we were to limit ourselves to Linux systems that might be an
option, but with the need to support OSX and Solaris [and in the
futute Windows] I don't see this as something viable. Portage is nice,
but it is the wrong tool for a cross platform toolchain. What we
currently have is very KISS, and KISS works :)

> Ted

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: Most Sage spkg's are out of date!

[mabshoff]

On Dec 28, 8:38 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>

Hi,

since nobody has stepped up yet I am volunteering to do this. I can
certainly need some help and am more than willing to share those
duties. Since I do most of the porting I would see this as a natural
fit since very often new spkgs cause trouble on the less common
platforms and being the person in charge that says no since some spkg
doesn't work on Solaris is a good thing. Just like patches we also
need some more testing of new/updated spkgs.

> > Are there some instructions for Sage package maintainers to follow?
> > I.e. what exact steps are neede to update the package?
>
> There are no instructions, and no master list of package maintainers, etc.
> One of the goals of this thread is to create such things.
>
> > 1) create a new spkg
> > 2) create a trac ticket and attach it? or expose the repository, so
> > that you can build it yourself?
> > 3) write to the mailinglist?
>
> We need:
>   (a)  a wiki page that lists packages with the corresponding maintainer.
>   (b) A natural system for updating patches.  I like your suggestion above,
> though _not_ the order.
>   (1) Create a trac ticket describing that the package is out of date.
> This should _already_ be done for every package I listed at
>  the beginning of this email.

I am doing that right now.

>   (2) Accept the trac ticket when you're about to make a new spkg.
>   (3) Post a link from the trac ticket to the new spkg (don't
> attach it, since
> it is too big.)
>   (4) Post to sage-devel announcing the new spkg and requesting
> feedback and testing.  Any such email *must* list some tests
> a user can try after "sage -i" 'ing the package to test that
> it actually installed OK.  All feedback from such testing
> should be pasted into the trac ticket.  The trac ticket should
> be assigned against an upcoming release of Sage.
>  (5)  The release manager puts the new spkg in Sage once it
> has got a positive review as a part of (4).
>
> Thoughts?

It will be a pain, but what are the alternatives? :)

>  -- William

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: Most Sage spkg's are out of date!

[Robert Bradshaw]

On Dec 28, 2007, at 8:28 PM, mabshoff wrote:

>>
>> We need:
>>   (a)  a wiki page that lists packages with the corresponding  
>> maintainer.
>>   (b) A natural system for updating patches.  I like your  
>> suggestion above,
>> though _not_ the order.
>>   (1) Create a trac ticket describing that the package is  
>> out of date.
>> This should _already_ be done for every package I  
>> listed at
>>  the beginning of this email.

1b. An explanation of why we should be updating. It'll probably be a  
huge drain on resources to update for every minor point change unless  
there are real improvements.


--~--~-~--~~~---~--~~
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: Most Sage spkg's are out of date!

[mabshoff]

On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
>  * cddlib: we ship 094b, but 094d is current.
#1619
>  * clisp: we ship clisp-2.41, but  2.43 is current  (I'm sure you can 
> comment!)
>  * cvxopt: we ship 0.9 but 0.9.1 is out.  It has "efficient Python
> classes for dense and sparse matrices (real and complex), with Python
> indexing and slicing and overloaded operations for matrix arithmetic"
#1620
> -- looks cool!
>  * gd: we ship 2.0.33 but 2.0.36 is current
#1621
>  * gfan: we ship 0.2.2 but 0.3 is current
#1010
>  * givaro: we ship 3.2.6 but 3.2.9 is current
#1035
>  * gmp: we ship 4.2.1 but 4.2.2 is current
#542
>  * gnutls: we ship 1.6.3 but 2.2.0 is current!
#1622
>  * gsl: we ship 1.9 but 1.10 is current
#1623
>  * jsmath: I don't even know what we ship (it's at most 3.4d), but
> current is 3.4f
#1624
>  * iml: we ship 1.0.1, but 1.0.2 is current (I think 1.0.2 is
> upstreaming our changes
> in a way that breaks things for us...)
#748
>  * ipython: we ship 0.8.1, but 0.8.2 is current
#1625
>  * lcalc: we ship 20070107, but 20070902 is current.
#1626
>  * libgcrypt: 1.4
#1627
>  * Maxima: we ship 5.13, but 5.14 is current.
#1470
>  * Moinmoin: we ship 1.5.7 but 1.5.8 is current
#1628
>  * numpy: we ship 1.0.3 but 1.0.4 is current
#1629
>  * opencdk: we ship 0.5.9 but 0.6.6 is current
#1630
>  * pari: we ship 2.3.2 but 2.3.3 is current (I posted a new spkg tonight)
#1603
>  * pexpect: we ship 2.0 but 2.3 is current (2.1 sucked (!); maybe 2.3 is 
> good??)
#502 - that one is quite old :)
>  * lippng: we ship 1.2.22, but 1.2.24 is current
tricky, no ticket yet.
>  * quaddouble: we ship 2.2, but 2.3.1 is current
#1631
>  * sqlite: we ship 3.5.3 but 3.5.4 is current
#1632
>  * sympy: we ship 0.5.7 but 0.5.9 is current
#1633
>  * zodb: we ship 3.7.0 but 3.7.2 is current
#1634


I think that Robert's last point about not just upgrading for the fun
of upgrading valid. But as the matplotlib episode shows even a point
release might fix bugs that we haven't fixed yet like the scale issue.
There is certainly a cost/benefit ratio and we shouldn't go nuts, but
I assume that many people do not actually report bugs from Sage and
its components.

I did work on the Cygwin port of 2.9.1.1 for the last 36 hours and
since I fixed some platform specific bugs for the n-th time (n>5 in
some cases) I would really like everybody who maintains a spkg to push
our fixes upstream and also establish a working relation ship with the
developers of said spkg.

Timothy Clemans has volunteered offlist to manage the wiki pages with
maintenance info.

I will subscribe the the announce mailing lists of all of the projects
we include in case I am not already on the mailing list :). We should
actually create something like that because if you do not read sage-
devel or sage-support chances are you might miss some release. It is
more and more my impression that people are slow to upgrade if a
release works for them, but that observation is besides the point
here.

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: Most Sage spkg's are out of date!

[William Stein]

On Dec 28, 2007 10:11 PM, mabshoff
<[EMAIL PROTECTED]> wrote:> we include
in case I am not already on the mailing list :). We should
> actually create something like that because if you do not read sage-
> devel or sage-support chances are you might miss some release. It is
> more and more my impression that people are slow to upgrade if a
> release works for them, but that observation is besides the point
> here.

There is a sage-announce mailing list.   It's listed here:

  http://sagemath.org/lists.html

 -- 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] Re: Fwd: About SAGE

[William Stein]

On Dec 28, 2007 6:16 PM, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> This does look perfect. Once this is set up, creating and uploading
> the iso should be a trivial task (done via a script), and if the
> artwork remained the same for all double-point releases that should
> be easy too, so I don't think a couple of dollars is worth the hassle
> of collecting and re-distributing it. I'll volunteer to set it up

Thanks!  I'm really glad you'll take charge for doing this, and that you think
you can make it so easy that no payment will be necessary.

The DVD should contain:
   (1) The SAGE HTML/PDF, etc., documentation
   (2) Source tarball
   (3) All the latest binaries and the vmware image.

> (though until 2.9.2 I'm going to be focusing on the 3d stuff).

Thanks!

 - 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~--~~~~--~~--~--~---

[sage-devel] #1635: lib->LIB symlink issue on OSX with binary Sage tar-ball

[mabshoff]

During my recent work on the Cygwin port I spend hours with
singular.spkg and found the probable cause for the lib->LIB symlink
issue on OSX. To quote #1635 [which I made a blocker for 2.9.2]:

The problem has come up a couple times on sage-devel: The OSX binary
Sage tar-ball contains a link case sensitive link lib->LIB that is
caused by the singular.spkg. I believe it is to accomodate some issue
with Singular's high level libraries. We should just skip creating
that link on OSX and all should be fine.

I will create an updated Singular.spkg in a little while and will
request testing for it.

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: Rosetta translations

[mabshoff]

Hi Tim,

On Dec 29, 3:22 am, root <[EMAIL PROTECTED]> wrote:
> >I think this is a great idea.

+1

> >What distribution license does the rosetta tex file have?
>
> Modified BSD.
>
> I'd like Sage to be in the list so people from other systems
> can have a clue what form they might type in Sage to get
> similar results.

I was wondering why the Rosetta document lists GMP as a system?

> Tim

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: Most Sage spkg's are out of date!

[Ted Kosan]

Michael wrote:

> Well, if we were to limit ourselves to Linux systems that might be an
> option, but with the need to support OSX and Solaris [and in the
> futute Windows] I don't see this as something viable. Portage is nice,
> but it is the wrong tool for a cross platform toolchain. What we
> currently have is very KISS, and KISS works :)

My understanding is that Portage can be used with OSX and Solaris:

http://www.gentoo.org/proj/en/gentoo-alt/prefix/

What came to mind was to subset the Portage tree to make a "Sage tree"
which only contains the software that Sage actually needs and then to
copy and extend the Gentoo tools (which are mostly written in python)
to serve the needs of Sage.

Anyway, this seemed like an interesting possibility to explore if it
was desired to automate the Sage build process at some point.

Ted

--~--~-~--~~~---~--~~
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: problem compiling sage (from at least 2.8.15 to 2.9.1.1)

[François Bissey]

On Sat, 29 Dec 2007, mabshoff wrote:
> On Dec 28, 8:36 pm, Francois <[EMAIL PROTECTED]> wrote:
> > Hello Michael,
>
> Hello Francois,
>
> > I think I found my problem. A little googling actually helped with
> > this link:http://bugs.archlinux.org/task/6864
> > I did some experiments with the intel _fortran_ compiler (not even the
> > C compiler)
> > and I still have it on my system.
> > Since the intel compiler doesn't compile my lattice QCD code correctly
> > anyway
> > I will remove it and try again.
> > I am busy for the next few hours so I will do that a bit latter.
>
> This is actually something we can prevent on our end by forcing SCons
> to use the GNU compilers instead of the Intel ones in case they are
> present. I had to fix similar issues on Solaris when Sun's compilers
> were installed and SCons picked those over gcc. Thanks for tracking
> this down. This is now
>
> http://trac.sagemath.org/sage_trac/ticket/1618
>
Nice! It was definitely ifc poisoning the build. libcsage builds fine now.

Thanks,
Francois

--~--~-~--~~~---~--~~
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: Most Sage spkg's are out of date!

[mabshoff]

On Dec 29, 7:33 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> Michael wrote:
> > Well, if we were to limit ourselves to Linux systems that might be an
> > option, but with the need to support OSX and Solaris [and in the
> > futute Windows] I don't see this as something viable. Portage is nice,
> > but it is the wrong tool for a cross platform toolchain. What we
> > currently have is very KISS, and KISS works :)

Hi Ted,

> My understanding is that Portage can be used with OSX and Solaris:
>
> http://www.gentoo.org/proj/en/gentoo-alt/prefix/

Well, but looking at

http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml

"simple" or "convinient" doesn't come to mind - :) - and that still
leaves Windows out in the cold.

> What came to mind was to subset the Portage tree to make a "Sage tree"
> which only contains the software that Sage actually needs and then to
> copy and extend the Gentoo tools (which are mostly written in python)
> to serve the needs of Sage.

That sounds like a monumental undertaking, especially since the
required tool set to start using portage is quite large.

> Anyway, this seemed like an interesting possibility to explore if it
> was desired to automate the Sage build process at some point.

I was under the impression that it already is automated ;). But adding
ebuild scripts and an overlay for Gentoo might be a first step to get
Sage into a distribution. You could beat Padus and certainly Debian to
the punch to be the first distribution that integrates Sage. And
Gentoo seems to be the perfect fit for a "compile from source" kind of
project.

> Ted

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: Most Sage spkg's are out of date!

[François Bissey]

On Sat, 29 Dec 2007, mabshoff wrote:
> Well, if we were to limit ourselves to Linux systems that might be an
> option, but with the need to support OSX and Solaris [and in the
> futute Windows] I don't see this as something viable. Portage is nice,
> but it is the wrong tool for a cross platform toolchain. What we
> currently have is very KISS, and KISS works :)
>
As a Gentoo-er myself I think a subset of portage would be very nice
to do the spkg job. It is in python, after all, which as we know is 
cross-platform. You also may not be aware but their is an effort dubbed 
Gentoo prefix to make it work on other platform than linux, even windows may 
be. freeBSD is quite advanced, I believe their is an effort on opensolaris 
(if it hasn't died) and there is definitely some effort to work with OS X.
Of course as I said at the beginning, sage probably only needs a subset of
portage it doesn't use flags for example.

Anyway that would be a major overhaul of the sage structure so it is very 
unlikely to happen :)

Francois

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