[sage-devel] Re: cool things coming up in matplotlib

On 08/04/09 00:58, Ondrej Certik wrote: >> I'm posting this since multiple people have touched this code in Sage, >> and might be interested in looking at a soon-to-be-native way to do it >> in matplotlib. > > Matplotlib guys rock. Btw, I just manage to get matplotlib working as > a traits editor

[sage-devel] Helpful Mercurial extensions

The following additions to ~/.hgrc will, e.g., automatically page and colorize the output from various hg commands (diff, status, qseries, etc.): [extensions] # http://mercurial.selenic.com/wiki/ColorExtension color= # http://mercurial.selenic.com/wiki/HighlightExtension hgext.highlight= # http:

[sage-devel] Re: Maplesoft sold to Japanese firm

On Mon, Aug 3, 2009 at 9:28 PM, Minh Nguyen wrote: > > Hi folks, > > Here's a news story about Maplesoft, the maker of Maple, being > acquired by Japanese comany Cybernet Systems. Thank you to Richard > Fateman for the link. > > http://news.therecord.com/Business/article/578473 > > -- You can see

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

rjf wrote: > The idea that one should "patch" the code in Maxima without knowing > what that code does (or should do) or that someone involved in the > Maxima project should make a substantive program content fix from one > version to another to make the ECL compiler happy --- when no other > co

[sage-devel] Re: Sage and Singular Talk

oh and forgot to mention, because of the way sage tries (and fails since Singular is very uncooperative) to map the points it knowns to points in Singular, the example above becomes (10,0,0,-1,0,3) (which again might change a sometimes since this depends on C[1][5]->POINTS). Now mapping this vect

[sage-devel] Maplesoft sold to Japanese firm

Hi folks, Here's a news story about Maplesoft, the maker of Maple, being acquired by Japanese comany Cybernet Systems. Thank you to Richard Fateman for the link. http://news.therecord.com/Business/article/578473 -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~

[sage-devel] Re: Sage and Singular Talk

The problem is that there is a place of degree 6 at position 0 (or 1 in Singular world). I think Singular used the places listed at C[3] for RR computations (if i am reading http://www.singular.uni-kl.de/Manual/latest/sing_1341.htm#SEC1418 correctly) and not C[1][5]->Points (which is random and d

[sage-devel] Re: passing graphs by value

On Mon, Aug 3, 2009 at 7:13 PM, Jason Grout wrote: > > Rado wrote: >> Let's try to divert the topic away from the embarrassing mistake i >> made:) >> >> For the graph editor I am still struggling with the update function, >> because the original graph variable name is lost once graph_editor is >>

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

On Mon, 03 Aug 2009 at 01:07PM -0400, Sébastien Labbé wrote: > I tried also to note every questions people were asking as well as every > thought I was having while giving the course : > > * SageTex Bug : Apparently, using \sage inside of a \caption in a figure > environnement doesn't work yet. >

[sage-devel] Re: passing graphs by value

Rado wrote: > Let's try to divert the topic away from the embarrassing mistake i > made:) > > For the graph editor I am still struggling with the update function, > because the original graph variable name is lost once graph_editor is > called. > > python function graph_editor(g) gets the graph

[sage-devel] Re: cool things coming up in matplotlib

kcrisman wrote: > Better axes would be so great. Will there be any support for native > log/semilog plots, an oft-requested feature (not by me)? See http://matplotlib.sourceforge.net/examples/pylab_examples/aspect_loglog.html http://matplotlib.sourceforge.net/examples/pylab_examples/log_bar.

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

Your implication that ECL should "note the error and then continue to compile" somehow reminds a recent thread (probably on sage-devel) where it was reported that some spkg sends compiler warnings to /dev/ null. Unless you can *prove* that the special circumstance ("static typing error in which a

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

I think it is worth pointing out that (a) The bug found is a static typing error in which a program which, in some circumstance, would do a list operation on an argument which is an integer. (b) This line of code in Maxima has probably been there for 35 years, and so far as anyone knows, that lin

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

2009/8/3 brandon.bar...@gmail.com : > > > I look forward to testing and building  it on opensolaris / intel. Give Sage a try on OpenSolaris and let me know what happens. I posted ealier today some notes on what I needed to do to get it build on SPARC. OpenSolaris might be a bit different. Things

[sage-devel] Re: cool things coming up in matplotlib

Better axes would be so great. Will there be any support for native log/semilog plots, an oft-requested feature (not by me)? Also, custom labeling of ticks (maybe that's already there)? Resolving all this would not only be better practice (using upstream instead of Sage-specific code, at least b

[sage-devel] Re: SAGE_FORTRAN and Fortran flags

On Mon, Aug 3, 2009 at 3:57 PM, Dr. David Kirkby wrote: > > William Stein wrote: >> On Mon, Aug 3, 2009 at 1:33 PM, Dr. David Kirkby >> wrote: >>> CC and CXX are set in Sage to default values if they are not specified. >>>  The readme says: >>> >>> - >>

[sage-devel] Re: SAGE_FORTRAN and Fortran flags

William Stein wrote: > On Mon, Aug 3, 2009 at 1:33 PM, Dr. David Kirkby > wrote: >> CC and CXX are set in Sage to default values if they are not specified. >> The readme says: >> >> - >> NOTE: If you're using Fortran on a platform without g95 binaries

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

I look forward to testing and building it on opensolaris / intel. On Aug 3, 4:21 pm, "Dr. David Kirkby" wrote: > Robert Dodier wrote: > > On Aug 3, 8:56 am, "Dr. David Kirkby" wrote: > > >> So we can expect 5.19 sometime in August, is that correct? Any rough > >> idea when it might be - first

[sage-devel] Re: graph editor for Sage

Hi Rado, On Tue, Aug 4, 2009 at 8:38 AM, Rado wrote: > > I have been sitting on this code for too long, so I think it would fit > in Sage's philosophy to release early, to include it in the next > version of Sage. Unfortunately, the feature merge window for Sage 4.1.1 has closed. Sage 4.1.1.rc1

[sage-devel] graph editor for Sage

I have been sitting on this code for too long, so I think it would fit in Sage's philosophy to release early, to include it in the next version of Sage. Here is my current version: http://www.math.uiuc.edu/~rkirov2/sage/graph_editor.zip it contains a diff patch for Sage devel and two files which

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 2:36 PM, William Stein wrote: > > On Mon, Aug 3, 2009 at 12:20 PM, bsdz wrote: >> >> On 3 Aug, 20:17, Ondrej Certik wrote: >>> On Mon, Aug 3, 2009 at 1:07 PM, William Stein wrote: >>> >> Also, what is the state of the windows port of Sage --- will it be >>> >> possible to j

[sage-devel] Re: SAGE_FORTRAN and Fortran flags

On Mon, Aug 3, 2009 at 1:33 PM, Dr. David Kirkby wrote: > > CC and CXX are set in Sage to default values if they are not specified. >  The readme says: > > - > NOTE: If you're using Fortran on a platform without g95 binaries included >       with Sage, e

[sage-devel] Re: passing graphs by value

On Aug 4, 5:21 am, Rado wrote: > Hello, > > (I apologize if this has been discussed and it is a design decision). > I just noticed that graphs are passed by value instead of passed by > reference (which i think is standard in python). > > example: > > sage:def modify(G): > sage:    G=graphs.Com

[sage-devel] Re: passing graphs by value

ops, my bad ... and i thought i knew python :) Rado On Aug 3, 4:04 pm, Kwankyu wrote: > On Aug 4, 5:21 am, Rado wrote: > > > > > Hello, > > > (I apologize if this has been discussed and it is a design decision). > > I just noticed that graphs are passed by value instead of passed by > > refere

[sage-devel] Re: passing graphs by value

Let's try to divert the topic away from the embarrassing mistake i made:) For the graph editor I am still struggling with the update function, because the original graph variable name is lost once graph_editor is called. python function graph_editor(g) gets the graph representation and sends it

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

Robert Dodier wrote: > On Aug 3, 8:56 am, "Dr. David Kirkby" wrote: > >> So we can expect 5.19 sometime in August, is that correct? Any rough >> idea when it might be - first half/second half of the month? > > I'll start turning out releases on the 5.19 branch -- 5.19.0, > 5.19.1, etc. Usually

[sage-devel] Re: passing graphs by value

On Mon, Aug 3, 2009 at 1:21 PM, Rado wrote: > > Hello, > > (I apologize if this has been discussed and it is a design decision). > I just noticed that graphs are passed by value instead of passed by > reference (which i think is standard in python). Graphs are pass by reference. Your function m

[sage-devel] Re: An improved spkg-install (for general usage)

On Sun, Aug 2, 2009 at 10:35 AM, Dr. David Kirkby wrote: > I noticed one package (lcalc) was passing GNU specific flags to the > assembler to suppress warnings. I've seen other packages send warning to > /dev/null. > > I decided to change the spkg-install for 'lcalc' somewhat, in a way that > I th

[sage-devel] SAGE_FORTRAN and Fortran flags

CC and CXX are set in Sage to default values if they are not specified. The readme says: - NOTE: If you're using Fortran on a platform without g95 binaries included with Sage, e.g., Itanium, you must use a system-wide gfortran. You hav

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 12:20 PM, bsdz wrote: > > On 3 Aug, 20:17, Ondrej Certik wrote: >> On Mon, Aug 3, 2009 at 1:07 PM, William Stein wrote: >> >> Also, what is the state of the windows port of Sage --- will it be >> >> possible to just maintain one spkg and it would build on windows, or >> >>

[sage-devel] Re: Using --enable-framework on Mac OS X?

On 3 Aug, 20:07, William Stein wrote: > On Mon, Aug 3, 2009 at 12:02 PM, Ondrej Certik wrote: > > > On Wed, May 13, 2009 at 10:46 AM, Brian Granger > > wrote: > > >> I just pinged the pythonmac-sig group about why and when a framework > >> build is actually needed.  A while back I created an spk

[sage-devel] passing graphs by value

Hello, (I apologize if this has been discussed and it is a design decision). I just noticed that graphs are passed by value instead of passed by reference (which i think is standard in python). example: sage:def modify(G): sage:G=graphs.CompleteGraph(4) sage:G=graphs.PetersenGraph() sage:mo

[sage-devel] Re: cool things coming up in matplotlib

On Sun, Aug 2, 2009 at 12:21 AM, Jason Grout wrote: > > Jason Grout wrote: >> Recently there was a thread that dealt with having axes of 2d plots >> cross at non-origin points.  This is a "problem" (depending on who is >> talking :) of the current Sage axis code. > > > It appears that the next ver

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 1:20 PM, bsdz wrote: > > On 3 Aug, 20:17, Ondrej Certik wrote: >> Is there some way to install openssh into windows, so that I can leave >> it running on my workstation somewhere and just use my terminal + ssh >> to log into there and port to windows using this approach? Th

[sage-devel] Re: Using --enable-framework on Mac OS X?

On 3 Aug, 20:17, Ondrej Certik wrote: > On Mon, Aug 3, 2009 at 1:07 PM, William Stein wrote: > >> Also, what is the state of the windows port of Sage --- will it be > >> possible to just maintain one spkg and it would build on windows, or > >> will it be necessary to maintain one spkg for linux/m

Re: [sage-windows] Re: [sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 1:07 PM, William Stein wrote: >> Also, what is the state of the windows port of Sage --- will it be >> possible to just maintain one spkg and it would build on windows, or >> will it be necessary to maintain one spkg for linux/mac and another >> one for windows? > > At pres

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 1:30 PM, Prabhu Ramachandran wrote: > > On 08/04/09 00:32, Ondrej Certik wrote: >>> I will dig up my framework python spkg and get back after I hear from >>> the pythonmac-sig folks. >> >> >> Could you please share it? I have created sip (sip is something like >> swig, neede

[sage-devel] Re: Python spkg for OSX framework build

On 07/10/09 01:55, William Stein wrote: >> I've made an SPKG of a framework Python build -- it was really easy. >> The modified spkg-install is on bsd.math.washington.edu as is the spkg, >> they are here: >> >> /Users/Prabhu/spkg-install.python >> /Users/Prabhu/python-2.6.2.p2.spkg >> >> I'm not g

[sage-devel] Re: Using --enable-framework on Mac OS X?

On 08/04/09 00:32, Ondrej Certik wrote: >> I will dig up my framework python spkg and get back after I hear from >> the pythonmac-sig folks. > > > Could you please share it? I have created sip (sip is something like > swig, needed to built pyqt) and pyqt packages here: Ondrej, I put up a simple

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Wed, May 13, 2009 at 10:46 AM, Brian Granger wrote: > > I just pinged the pythonmac-sig group about why and when a framework > build is actually needed.  A while back I created an spkg for qt/pyqt > and I remember that I needed to do a framework build to get it to > work.  My recollection is th

[sage-devel] Re: Using --enable-framework on Mac OS X?

On Mon, Aug 3, 2009 at 12:02 PM, Ondrej Certik wrote: > > On Wed, May 13, 2009 at 10:46 AM, Brian Granger > wrote: >> >> I just pinged the pythonmac-sig group about why and when a framework >> build is actually needed.  A while back I created an spkg for qt/pyqt >> and I remember that I needed to

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

> > * I try to do some search in the sage-devel group from its own web page, but > > it apparently finds only the very recent messages. For example, searching > > "Siena" doesn't show me the message Franco wrote about the talk he gave in > > University of Siena : "Your search - Siena - did not ma

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

On 3 Aug., 20:28, Simon King wrote: > Hi Sébastien, > > But there *is* an interface to sage in sage. It is called sage0, and > it works as expected. Since I don't have Maple, I use Singular: > > sage: A = matrix(2,[1..4]) > sage: B = singular(A) > sage: C = B.sage() > sage: D = sage0(B) > sage: C

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

Hi Sébastien, On 3 Aug., 19:44, William Stein wrote: ... > > * The same somebody likes the idea of defining in Sage object and translate > > it from one system to the other. One reason is that he told me that he > > prefers the sage latex output for some object. I think translation of > > object

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

On Aug 3, 8:56 am, "Dr. David Kirkby" wrote: > So we can expect 5.19 sometime in August, is that correct? Any rough > idea when it might be - first half/second half of the month? I'll start turning out releases on the 5.19 branch -- 5.19.0, 5.19.1, etc. Usually the branch stabilizes after 2 or

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

On Mon, Aug 3, 2009 at 10:07 AM, Sébastien Labbé wrote: > Hi Sage-devel, > > I gave a 3-days Sage formation in Montreal on July 14, 15 and 16th that I > like to call "Jours Sage au LaCIM" : > > http://wiki.sagemath.org/SébastienLabbé/JoursSageUQAM > > We could say that this formation corresponds t

[sage-devel] Re: The 3-days Sage Formation I gave + Feedbacks and thoughts

On Mon, Aug 3, 2009 at 10:07 AM, Sébastien Labbé wrote: > Hi Sage-devel, > > I gave a 3-days Sage formation in Montreal on July 14, 15 and 16th that I > like to call "Jours Sage au LaCIM" : > > http://wiki.sagemath.org/SébastienLabbé/JoursSageUQAM > > We could say that this formation corresponds t

[sage-devel] The 3-days Sage Formation I gave + Feedbacks and thoughts

Hi Sage-devel, I gave a 3-days Sage formation in Montreal on July 14, 15 and 16th that I like to call "Jours Sage au LaCIM" : http://wiki.sagemath.org/SébastienLabbé/JoursSageUQAM We could say that this formation corresponds to "Qu

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

Robert Dodier wrote: > William Stein wrote: > >> +1 Make packages so that everything works, but don't include them in >> sage-4.1.1. When will the next Maxima come out? Maybe that's for >> sage-4.2 or sage-4.1.2? > > I'm on the verge of making the Maxima 5.19 release branch > (today or tom

[sage-devel] [Fwd: Re: [Ecls-list] Status of ports and release candidate]

As you can see, a new ECL will be out soon. This will fix the Solaris issues, but will break Maxima unless it is patched some way. Dave --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send

[sage-devel] Re: Warnings on development releases

On Mon, Aug 3, 2009 at 7:29 AM, slabbe wrote: > > Hi, > > My feeling is that adding the sentence > > "WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE" > > to a prerelease but not for a stable Sage version evokes that we can > trust all the results from the stable one. > +1. It definit

[sage-devel] Re: [Maxima] Patches for building Maxima with ECL

On 8/3/09, Juan Jose Garcia-Ripoll wrote: > Using these patches, Maxima builds and installs just fine using the > unstable (git/CVS) sources of ECL, which will conform the upcoming > 9.8.1 release. Please take them into consideration. I'll try these patches and if they work OK then I'll commit

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

William Stein wrote: > +1 Make packages so that everything works, but don't include them in > sage-4.1.1. When will the next Maxima come out? Maybe that's for > sage-4.2 or sage-4.1.2? I'm on the verge of making the Maxima 5.19 release branch (today or tomorrow). I'll try the patches from

[sage-devel] Re: Warnings on development releases

Hi, My feeling is that adding the sentence "WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE" to a prerelease but not for a stable Sage version evokes that we can trust all the results from the stable one. But I'm sure there is still one bug to be fixed even in a stable Sage version.

[sage-devel] Re: Patches for building Maxima with ECL

Juan Jose Garcia-Ripoll wrote: > 2) There is a serious bug in src/db.lisp, passing an integer as an > argument to CAR. ECL's new type propagation code has detected it. I > have provided a reasonable fix. I stand in awe. src/db.lisp is probably the most obscure of all the obscure code in Maxima.

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

William Stein wrote: > On Mon, Aug 3, 2009 at 6:18 AM, David Joyner wrote: >> On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkby >> wrote: >>> I need some guidance on what do about some issues we have. I'll >>> summarise, since not everyone is going to be aware of them. >>> >>> 1) Sage will not bui

[sage-devel] Re: An improved spkg-install (for general usage)

On Mon, Aug 3, 2009 at 4:16 AM, Dr. David Kirkby wrote: > > William Stein wrote: >> On Sun, Aug 2, 2009 at 9:35 AM, Dr. David Kirkby >> wrote: >>> I noticed one package (lcalc) was passing GNU specific flags to the >>> assembler to suppress warnings. I've seen other packages send warning to >>> /

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

David Joyner wrote: > On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkby > wrote: >> I need some guidance on what do about some issues we have. I'll >> summarise, since not everyone is going to be aware of them. >> >> 1) Sage will not build on Solaris SPARC due to issues in the latest >> official e

[sage-devel] Re: [Ecls-list] We have an 'ecl' which builds on Solaris SPARC !!!

On Mon, Aug 3, 2009 at 1:49 AM, Dr. David Kirkby wrote: > > Juan Jose Garcia-Ripoll wrote: >> On Mon, Aug 3, 2009 at 9:28 AM, Dr. David Kirkby >> wrote: >>> I believe he still has some issues on Solaris Intel using gcc 4.4.1. >>> That version of gcc was only released on 22nd July 2009 (< 2 weeks

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

On Mon, Aug 3, 2009 at 6:18 AM, David Joyner wrote: > > On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkby > wrote: >> >> I need some guidance on what do about some issues we have. I'll >> summarise, since not everyone is going to be aware of them. >> >> 1) Sage will not build on Solaris SPARC due

[sage-devel] Re: is the wiki down?

On Mon, Aug 3, 2009 at 5:00 AM, Minh Nguyen wrote: > > Hi folks, > > It looks like the Sage wiki at > > wiki.sagemath.org > > is down. My attempt to access it results in the message "Service > Temporarily Unavailable". But if I ping it, then I don't get any > packet loss. I've restarted the wiki

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkby wrote: > > I need some guidance on what do about some issues we have. I'll > summarise, since not everyone is going to be aware of them. > > 1) Sage will not build on Solaris SPARC due to issues in the latest > official ecl. (It is not the only issu

[sage-devel] Re: Warnings on development releases

Dr. David Kirkby wrote: > John H Palmieri wrote: >> On Aug 2, 11:19 am, "Dr. David Kirkby" >> wrote: >>> If there were only pre-release versions of Sage available, and no stable >>> release, then a less prominent message may be ok. But when there are >>> stable releases, and someone is using one

[sage-devel] Re: Should there be a permanent link to the latest pre-release?

Dr. David Kirkby wrote: > As far as I'm aware, the latest pre-release is at > > http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.rc0.tar > > Would do people think about the idea of a permanent link to whatever is > the latest development release? It should be quite easy to do. If a

[sage-devel] Sage builds on Solaris SPARC with gcc 4.4.0 (with a few hacks)

I managed to get Sage 4.1.1.rc0 to build on a SPARC based Sun workstation of mine, with a few hacks. The machine is sun4u, runs Solaris 10 update 7 and gcc 4.4.0 I've not tried on 't2' yet. I will try that later today, so others can have a play. But this machine is a bit quicker than t2 and be

[sage-devel] Re: [sage-release] Re: Sage 4.1.1.alpha1 released

Hi Georg, On Mon, Aug 3, 2009 at 9:48 PM, gsw wrote: > >> ... >> >> Trying: >> set_random_seed(0L) >> Expecting nothing >> ok >> Trying: >> change_warning_output(sys.stdout) >> Expecting nothing >> ok >> Trying: >> r.completions('tes')###line 838:_sage_>>> r.completions('tes') >>

[sage-devel] is the wiki down?

Hi folks, It looks like the Sage wiki at wiki.sagemath.org is down. My attempt to access it results in the message "Service Temporarily Unavailable". But if I ping it, then I don't get any packet loss. -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post t

[sage-devel] Re: What do we do about the Maxima / ecl / Solaris issues?

Dr. David Kirkby wrote: > I need some guidance on what do about some issues we have. I'll > summarise, since not everyone is going to be aware of them. > > 1) Sage will not build on Solaris SPARC due to issues in the latest > official ecl. (It is not the only issue, but is one of them). > > 2)

[sage-devel] What do we do about the Maxima / ecl / Solaris issues?

I need some guidance on what do about some issues we have. I'll summarise, since not everyone is going to be aware of them. 1) Sage will not build on Solaris SPARC due to issues in the latest official ecl. (It is not the only issue, but is one of them). 2) The ecl developers have solved that,

[sage-devel] Re: An improved spkg-install (for general usage)

William Stein wrote: > On Sun, Aug 2, 2009 at 9:35 AM, Dr. David Kirkby > wrote: >> I noticed one package (lcalc) was passing GNU specific flags to the >> assembler to suppress warnings. I've seen other packages send warning to >> /dev/null. >> >> I decided to change the spkg-install for 'lcalc'

[sage-devel] Patches for building Maxima with ECL

The patches attached cover the following to problems: 1) Due to different fixes towards better ANSI compliance, ECL's compile-file-pathname has changed behavior and when passed :output-file it preserves the pathname. This breaks the current assumptions in Maxima's build process 2) There is a seri

[sage-devel] Re: [Ecls-list] We have an 'ecl' which builds on Solaris SPARC !!!

Juan Jose Garcia-Ripoll wrote: > On Mon, Aug 3, 2009 at 9:28 AM, Dr. David Kirkby > wrote: >> I believe he still has some issues on Solaris Intel using gcc 4.4.1. >> That version of gcc was only released on 22nd July 2009 (< 2 weeks ago). > > Seems 4.4.1 is doing fine after I reverted some chang

[sage-devel] Re: [Ecls-list] We have an 'ecl' which builds on Solaris SPARC !!!

On Mon, Aug 3, 2009 at 9:28 AM, Dr. David Kirkby wrote: > I believe he still has some issues on Solaris Intel using gcc 4.4.1. > That version of gcc was only released on 22nd July 2009 (< 2 weeks ago). Seems 4.4.1 is doing fine after I reverted some changes from MPIR back into GMP. The tests are

[sage-devel] We have an 'ecl' which builds on Solaris SPARC !!!

Juanjo (one of the main ecl developers) has put a *lot* of effort into sorting out the Solaris issues with ecl. I'd like to publicly thank him for his efforts. I believe he still has some issues on Solaris Intel using gcc 4.4.1. That version of gcc was only released on 22nd July 2009 (< 2 week