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

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

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

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

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

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, b

[sage-devel] Re: "sage" google pagerank

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 hopel

[sage-devel] Re: "sage" google pagerank

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 unsubs

[sage-devel] Re: Fwd: cremona package under Sage

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-devel] Re: sage-2.9.2

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, b

[sage-devel] GUI widgets in the notebook (was sage-2.9.2)

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

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

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

[sage-devel] Re: sage-2.9.2

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,

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

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

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

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 th

[sage-devel] Re: Fwd: About SAGE

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.

[sage-devel] Rosetta translations

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 an

[sage-devel] Re: [Axiom-developer] Rosetta translations

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 > curren

[sage-devel] Re: Fwd: About SAGE

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

[sage-devel] Re: [Axiom-developer] Rosetta translations

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

[sage-devel] Re: Fwd: [Jmol-developers] [sage-devel] Re: Jmol and Mathematics Visualization

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

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

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 instructio

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

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 dis

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

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) >

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

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 L

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

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

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

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 ticke

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

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

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

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 impr

[sage-devel] Re: Fwd: About SAGE

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

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

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

[sage-devel] Re: Rosetta translations

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

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

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 > c

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

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

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

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, >

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

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 t