Hi John,
On Mon, Sep 28, 2009 at 7:57 AM, John Cremona wrote:
>
> Two test failures on 32-bit ubuntu:
>
>sage -t "devel/sage/sage/crypto/boolean_function.pyx"
I think this is a 32- vs. 64-bit issue. On various 64-bit platforms,
all doctests in that module pass. But on 32-bit platforms,
Hi,
I spent several hours yesterday trying to get matplotlib for Sage to
work on OS X 10.6. On my laptop everything works perfectly, but on
another test machine (bsd.math) the workaround from my laptop doesn't
work. So at this point Sage still does not support OS X 10.6.
The problem is in matp
Hi Japp,
On Mon, Sep 28, 2009 at 5:29 AM, Jaap Spies wrote:
> On Fedora 11, 32 bit build failed on sage:
> An error occurred while installing pari-2.3.3.p1
>
> I had a fix for alpha1 but this did not get into alpha4
> apparently.
I don't remember seeing a ticket for that. Can you please rem
On Sep 25, 6:32 pm, William Stein wrote:
> On Fri, Sep 25, 2009 at 6:01 PM, Peter wrote:
>
> > Hi,
>
> > I really like the canvas3d plot option in 4.1.2 since it will make it
> > easier to implement interactive 3d scenes in Sage and make them also
> > display in browsers that do not support ja
On Sep 25, 6:32 pm, William Stein wrote:
> On Fri, Sep 25, 2009 at 6:01 PM, Peter wrote:
>
> > Hi,
>
> > I really like the canvas3d plot option in 4.1.2 since it will make it
> > easier to implement interactive 3d scenes in Sage and make them also
> > display in browsers that do not support ja
Hi David,
On Mon, Sep 28, 2009 at 11:19 AM, Dr. David Kirkby
wrote:
>
> There has been a few recent changes to the libgcrypt .spkg file. I
> incorporated some changes which allowed this to build on Sun Studio, but
> appeared to have created two copies of the source code by mistake.
I think the
I had those two failures plus two in cell.py:
File "/Volumes/E/sage-4.1.2.alpha4/devel/sage/sage/server/notebook/
cell.py", line 1601:
sage: C.introspect_html()
Expected:
'...foobar...'
Got:
'foobar'
and:
File "/Volumes/E/sage-4.1.2.alpha4/devel/sage/sage/server/notebook/
cell.py",
There has been a few recent changes to the libgcrypt .spkg file. I
incorporated some changes which allowed this to build on Sun Studio, but
appeared to have created two copies of the source code by mistake.
Ming fixed the duplicate code at http://sagetrac.org/sage_trac/ticket/6758
but did not a
Hi all,
Found this on the web: A Trillion Triangles
http://www.aimath.org/news/congruentnumbers/
Cheers,
Jaap
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-de
Hi,
I've made http://uw.sagenb.org/ a demo of the new standalone Sage
notebook.Please try it and report *all* bugs. I'll release it
when I fix all bugs that aren't already bugs in the current notebook.
Some known issues that aren't worth reporting:
* introspection does not show Sphinx
Hi Matthew,
Glad to see someone else interested in the same idea. I prefer not to
get into assembling/building software myself to do the job, but would
like to use a packaged solution, preferably open source. One issue is
that I don't have the skill or the inclination, and another reason is
long-
No FLINT only requires C99, so 3.4.3 is fine I believe.
I think FLINT 2 will drop the C99 requirement as it is a damned pain
in the neck, as MSVC is no C99 compliant. Probably by the time I get
FLINT 2 release they'll release MSVC 2010 and spring C99 compliance on
us, only 11 years after the stan
Two test failures on 32-bit ubuntu:
sage -t "devel/sage/sage/crypto/boolean_function.pyx"
sage -t "devel/sage/sage/rings/polynomial/pbori.pyx"
sage -t "devel/sage/sage/crypto/boolean_function.pyx"
**
File "/ho
2009/9/27 William Stein :
ey learn is Linux.
>
> Carlo posted this a few messages back:
>
> http://www.ee.surrey.ac.uk/Teaching/Unix/
>
> I flipped through it a bit, and it looks excellent. And moreover, I think it
> does a great job of emphasizing the difference between UNIX and "Linux".
>
It
On Sat, Sep 26, 2009 at 7:14 PM, Minh Nguyen wrote:
>
> Hi,
>
> On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
>
>
>
>> On related notes, should we
>>
>> * Re-organize the Sage wiki front page? For example:
>>
>> + Make it easier for a newcomer, developer or user, to find what they
>
On Sun, Sep 27, 2009 at 3:43 AM, Maurizio wrote:
>
> Hi all,
> let me catch this notebook refactoring to ask for something that just
> came to my mind.
>
> Let's assume you have any kind of design or analysis process flow, one
> great thing I'd like to have is the chance to define some input
> va
On Sun, Sep 27, 2009 at 5:07 AM, Dr. David Kirkby
wrote:
>
> Using
>
> * Solaris 10 update 7 on SPARC
> * sage-4.1.2.alpha2
> * Sun Studio 12.1
> * An updated configure script to allow the Sun compiler to be used,
> I found that matplotlib-0.99.0 will not build.
>
> This is now ht
On Sun, Sep 27, 2009 at 2:04 PM, Serge A. Salamanka wrote:
>
> William Stein wrote:
>>
>> In the notebook separation, it has been a fine line between rewriting
>> things (which takes longer) and just leaving them possibly suboptimal.
>> One thing I did was completely rewrite everything that use
On Sun, Sep 27, 2009 at 2:12 PM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>
>>> Just to add that even the very latest release of Solaris (Solaris 10
>>> update 7) on SPARC only ships with gcc 3.4.3. Users using SPARC
>>> hardware are unlikely to have root access as it tends not to be us
> Looking at spkg/base/prereq-0.3-install (the file I just updated) to
> 0.4 I see:
>
> ---
> if [ "$SAGE_PORT" = "" ]; then
> if [ `uname | sed -e 's/WIN.\+/WIN/'` = "CYGWIN" ]; then
> echo "Building or using SAGE with Cygwin is absolutely definitely"
> echo "n
William Stein wrote:
>> Just to add that even the very latest release of Solaris (Solaris 10
>> update 7) on SPARC only ships with gcc 3.4.3. Users using SPARC
>> hardware are unlikely to have root access as it tends not to be used by
>> home users too much (yours truly is a bit of an exception
William Stein wrote:
>
> In the notebook separation, it has been a fine line between rewriting
> things (which takes longer) and just leaving them possibly suboptimal.
> One thing I did was completely rewrite everything that used pexpect,
> so the notebook doesn't depend on the sage/interfaces/
On Sun, Sep 27, 2009 at 2:54 AM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>> On Sun, Sep 27, 2009 at 12:13 AM, Minh Nguyen wrote:
>
>> FOR supporting 3.4.x:
>>
>> [ ] It probably would be easy at this point, since it just means
>> fixing ratpoints.
>>
>> [ ] This reminds me of when w
William Stein wrote:
> On Sun, Sep 27, 2009 at 12:48 PM, Dr. David Kirkby
> wrote:
>> William Stein wrote:
>>> On Sun, Sep 27, 2009 at 9:31 AM, Dr. David Kirkby
>>> wrote:
The spkg-install for gap-4.4.10.p12 says
echo "*WARNING*: Unsetting CC since that tends to break GAP bui
On Sun, Sep 27, 2009 at 6:38 AM, Dr. David Kirkby
wrote:
>
> Using
>
> * Solaris 10 update 7 on SPARC
> * sage-4.1.2.alpha2
> * Sun Studio 12.1
> * An updated configure script to allow the Sun compiler to be used
>
> I found that pynac-0.1.8.p2 will not build. It appears the Sun C
On Sun, Sep 27, 2009 at 7:53 AM, Dr. David Kirkby
wrote:
>
> Using
>
> * Solaris 10 update 7 on SPARC
> * sage-4.1.2.alpha2
> * Sun Studio 12.1
> * An updated configure script to allow the Sun compiler to be used
> http://sagetrac.org/sage_trac/ticket/7021
>
> CC was set to the Su
On Sun, Sep 27, 2009 at 1:24 PM, ahmet alper parker wrote:
>
> This is just a recommandation on the topic. Personally, i don' believe
> if someoneone try to learn linux/unix/minix (whatever you call) will
> learn it correctly from the available online literature. Generally,
> they have a misunde
On Sun, Sep 27, 2009 at 12:48 PM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>> On Sun, Sep 27, 2009 at 9:31 AM, Dr. David Kirkby
>> wrote:
>>>
>>>
>>> The spkg-install for gap-4.4.10.p12 says
>>>
>>> echo "*WARNING*: Unsetting CC since that tends to break GAP building"
>>> unset CC echo "
This is just a recommandation on the topic. Personally, i don' believe
if someoneone try to learn linux/unix/minix (whatever you call) will
learn it correctly from the available online literature. Generally,
they have a misunderstanding that everything they learn is Linux.
Maybe writing something
On Sun, Sep 27, 2009 at 12:17 PM, Harald Schilly
wrote:
> yes, i can do that. this week i'm a little bit short on time, but i
> can do it. is there already something online? just tell me any details
> that might be necessary to know, like the repository or mailing list,
> and i can set it up.
OK
William Stein wrote:
> On Sun, Sep 27, 2009 at 9:31 AM, Dr. David Kirkby
> wrote:
>>
>>
>> The spkg-install for gap-4.4.10.p12 says
>>
>> echo "*WARNING*: Unsetting CC since that tends to break GAP building"
>> unset CC echo "*WARNING*: Unsetting CXX since that tends to break GAP
>> building" uns
Minh Nguyen wrote:
> Hi folks,
>
> Yes, you heard right. It's Sage 4.1.2.alpha4, not 4.1.2.alpha3. Sage
> 4.1.2.alpha3 was released by William Stein for working on making the
> notebook a self-contained package. The source tarball for Sage
> 4.1.2.alpha4 is up at
>
> http://sage.math.washington.
On Sun, Sep 27, 2009 at 9:31 AM, Dr. David Kirkby
wrote:
>
>
>
> The spkg-install for gap-4.4.10.p12 says
>
> echo "*WARNING*: Unsetting CC since that tends to break GAP building"
> unset CC echo "*WARNING*: Unsetting CXX since that tends to break GAP
> building" unset CXX
>
> This appears to be
On Sun, Sep 27, 2009 at 11:34 AM, Jonathan wrote:
>
> Bob Hanson (the lead Jmol developer) has verified that replacing
> the .innerHTML within a div containing Jmol with plain html does
> destroy the applet and free up memory. Thus my suggestion should
> work. I haven't got any example clean co
On Sun, Sep 27, 2009 at 11:31 AM, Ondrej Certik wrote:
> On Sun, Sep 27, 2009 at 11:25 AM, William Stein wrote:
>> Harald,
>>
>> Is there any chance you could design a website for "The Sage Notebook"
>> as a separate project from Sage, kind of like how
>> http://pynac.sagemath.org/ is a separate
Hi Hazem,
I'm somewhat new to using SAGE, but in my research group we're all
picking it (and the FEMhub project) up pretty quickly. I think a hub
like this would be a great idea, and it's something I've been thinking
about as well. A light Turbogears backend for a document storage
system would
Bob Hanson (the lead Jmol developer) has verified that replacing
the .innerHTML within a div containing Jmol with plain html does
destroy the applet and free up memory. Thus my suggestion should
work. I haven't got any example clean code yet. I might get to it
this evening, but no promises.
Jo
John Cremona wrote:
>> However, perhaps things might change in the Winter. I have run an old
>> Sun in the garage just to raise the temperature a bit to stop the water
>> freezing! I guess I could use the IBM or HP machine to do the same this
>
> I think that is brilliant.
I'm glad you like it
>
> However, perhaps things might change in the Winter. I have run an old
> Sun in the garage just to raise the temperature a bit to stop the water
> freezing! I guess I could use the IBM or HP machine to do the same this
I think that is brilliant. Perhaps you should tell Sun about that --
they
On Sep 27, 3:32 pm, Marmaduke wrote:
> I learned most useful things from the Info pages on coreutils. Maybe
> these can be rendered to html because they come from Texinfo?
look here: http://www.gnu.org/software/coreutils/manual/html_node/
h
--~--~-~--~~~---~--~~
The spkg-install for gap-4.4.10.p12 says
echo "*WARNING*: Unsetting CC since that tends to break GAP building"
unset CC echo "*WARNING*: Unsetting CXX since that tends to break GAP
building" unset CXX
This appears to be done by Michael Abshoff as SPKG.txt shows:
gap-4.4.10.p8 (Michael Abshof
On Sep 26, 6:05 pm, Robert Bradshaw
wrote:
> On Sep 26, 2009, at 3:45 PM, lutusp wrote:
>
>
>
> > I 'm in the process of writing a Sage tutorial at http://
> > arachnoid.com/sage.
> > I'm about about halfway through the project, the completed pages may
> > be a useful resource, and I wanted to (1
Minh Nguyen wrote:
> Your updated spkg at ticket #7021 [1] is certainly a huge improvement.
> I haven't studied the code in much detail. But on a cursory glance it
> does improve the detection of various necessary tools for building
> Sage. I have been building Sage 4.1.2.alpha4 with the spkg's a
This is now http://sagetrac.org/sage_trac/ticket/7040
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C compiler. Th
This is now trac http://sagetrac.org/sage_trac/ticket/7039
I'm using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
Some time ago I sorted out
This is now http://sagetrac.org/sage_trac/ticket/7038
I gather ratpoints is causing problems with it wanting a very recent
version of gcc, well here is another issue. Even if the variable CC is
set to the Sun compiler, ratpoints ignores that and simply uses gcc
anyway.
It seems a bit funny to
Dr. David Kirkby wrote:
> Using
>
> * Solaris 10 update 7 on SPARC
> * sage-4.1.2.alpha2
> * Sun Studio 12.1
> * An updated configure script to allow the Sun compiler to be used
> http://sagetrac.org/sage_trac/ticket/7021
>
> CC was set to the Sun C compiler. Despite thousan
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C compiler. Despite thousands of lines of C code
being built, libm4r
Hi John,
On Sun, Sep 27, 2009 at 8:51 AM, John H Palmieri wrote:
> In an attempt to save time, I attempted to build using all of these at
> once (instead of doing one at a time), along with the new fortran spkg
> (#6981) and the new r spkg (#6972).
I was lazy and did the same thing. Great mi
Dr. David Kirkby wrote:
> http://sagetrac.org/sage_trac/ticket/7036
I made a correction to that. This is C++ code, so its CXX that is being
ignored, not CC
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe f
http://sagetrac.org/sage_trac/ticket/7036
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C compiler, CXX to the Sun
Hi David,
On Mon, Sep 28, 2009 at 1:20 AM, Dr. David Kirkby
wrote:
>
> Using the updated configure script at
>
> http://sagetrac.org/sage_trac/ticket/7021
>
> with the Sun compiler, sure shows up a few problems, many of which
> involving ignoring CC and CXX, which wont be Solaris specific.
Y
This report is now
http://sagetrac.org/sage_trac/ticket/7035
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C comp
Minh Nguyen wrote:
> Hi David,
>
> On Mon, Sep 28, 2009 at 1:09 AM, Dr. David Kirkby
> wrote:
>
>
>
>> This is trac http://sagetrac.org/sage_trac/ticket/7034
>> For some reason, the title of that trac item has got messed up, and I
>> can't change it. The title of this email would be quite sen
Hi David,
On Mon, Sep 28, 2009 at 1:09 AM, Dr. David Kirkby
wrote:
> This is trac http://sagetrac.org/sage_trac/ticket/7034
> For some reason, the title of that trac item has got messed up, and I
> can't change it. The title of this email would be quite sensible, if
> anyone knows how to chan
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C compiler, and CXX to the Sun C++ compiler,
It would appear that Us
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
http://sagetrac.org/sage_trac/ticket/7021
CC was set to the Sun C compiler, and CXX to the Sun C++ compiler,
checking whether we are
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
(#7021)
CC was set to the Sun C compiler, and CXX to the Sun C++ compiler. It's
apparent that singular is ignoring CC and using gcc
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
(#7021)
CC was set to the Sun C compiler, and CXX to the Sun C++ compiler. The
singular configure script does not believe the Sun C+
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
CC was set to the Sun C compiler, and CXX to the Sun C++ compiler,
The 'quaddouble-2.2.p9' package believes the Sun C++ compiler can'
On Sat, Sep 26, 2009 at 9:12 PM, William Stein wrote:
> Are there any amazingly good freely available introductions to basic
> command line UNIX that people recommend. I've noticed that many
> people (often young students raised on Windows) who really want to
> work on Sage don't know anything a
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used
I found that pynac-0.1.8.p2 will not build. It appears the Sun C++
compiler simply does not like the C++ code in pynac 0.1.8.p2
This
I learned most useful things from the Info pages on coreutils. Maybe
these can be rendered to html because they come from Texinfo?
On Sep 26, 7:12 pm, William Stein wrote:
> Hi,
>
> Are there any amazingly good freely available introductions to basic
> command line UNIX that people recommend. I
Minh Nguyen wrote:
> The packages you have updated so far all contain a similar set of
> tests at the start of the file spkg-install. To me, those tests look
> very much like a template to be used for perhaps all the other spkg's.
> It would be very beneficial to package maintainers if those boil
Hi David,
On Sun, Sep 27, 2009 at 10:43 PM, Dr. David Kirkby
wrote:
> The fact is the Sun linker seems better than the GNU one. The problem is
> that some code sends GNU-specific options to the Sun linker, which
> fails. However, I believe I have sorted all them out in Sage as long as
> gcc i
Hi folks,
Yes, you heard right. It's Sage 4.1.2.alpha4, not 4.1.2.alpha3. Sage
4.1.2.alpha3 was released by William Stein for working on making the
notebook a self-contained package. The source tarball for Sage
4.1.2.alpha4 is up at
http://sage.math.washington.edu/home/mvngu/release/upgrade/sage
Carlo Hamalainen wrote:
> On Sun, Sep 27, 2009 at 1:48 PM, Minh Nguyen wrote:
>>> However, I thought someone said once that Flint also needed a 4.x
>> I don't know about that. Better check with Bill Hart on the minimum
>> version of GCC for compiling FLINT.
>
> I was able to compile gcc 4.2.4 on
On Sun, Sep 27, 2009 at 1:48 PM, Minh Nguyen wrote:
>> However, I thought someone said once that Flint also needed a 4.x
>
> I don't know about that. Better check with Bill Hart on the minimum
> version of GCC for compiling FLINT.
I was able to compile gcc 4.2.4 on Solaris 10 x86 but had no luck
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used,
I found that matplotlib-0.99.0 will not build.
This is now http://sagetrac.org/sage_trac/ticket/7028
CC was set to the Sun C comple
Maurizio wrote :
> At the beginning of the worksheet I could write in a cell something like:
>
> a,b = "any live data"
>
> So, three cells later I have:
>
> c = a + b; c
>
> And whenever I update a or b, the evaluation of that cell is repeated
> and c gets updated accordingly...
With students all
Hi David,
On Sun, Sep 27, 2009 at 7:54 PM, Dr. David Kirkby
wrote:
> Just to add that even the very latest release of Solaris (Solaris 10
> update 7) on SPARC only ships with gcc 3.4.3. Users using SPARC
> hardware are unlikely to have root access as it tends not to be used by
> home users
Using
* Solaris 10 update 7 on SPARC
* sage-4.1.2.alpha2
* Sun Studio 12.1
* An updated configure script to allow the Sun compiler to be used.
I find that 'f2c' is ignoring the CC variable. This is now
http://sagetrac.org/sage_trac/ticket/7027
f2c-20070816.p1/src/libf2c/._z
Since building a configure script which allows one to attempt to build
Sage with Sun Studio, I discovered that linbox thinks GMP is not
installed, even though it appears to be.
This is
http://sagetrac.org/sage_trac/ticket/7026
and is very similar to
http://sagetrac.org/sage_trac/ticket/7025
Here's another issue noticed when trying to build Sage sage-4.1.2.alpha2
with Sun Studio. It is a bit of an odd one too. Despite mpir having been
installed properly (gmp the header and library files are present),
givaro exits at the configure stage, as it believes GMP >= 3.1.1 does
not exist.
Since producing a new 'configure' script that allows one to attempt to
build Sage with Sun's compiler, not surprisingly I found a few packages
which ignore the fact CC and CXX are set, and do their own thing anyway.
Flint is one of them.
flint-1.3.0.p2/src/profiler.h
flint-1.3.0.p2/src/mpn_ex
I added a zip file with the code to my sagemath directory and a note
to the trac server. Thanks for your comments Georg and Robert
Bradshaw! I think I'll need some help making the build scripts for
every possible operating system and platform. Thanks for being
patient with this being my first S
Hi all,
let me catch this notebook refactoring to ask for something that just
came to my mind.
Let's assume you have any kind of design or analysis process flow, one
great thing I'd like to have is the chance to define some input
variables to be equal to a value that, whenever is updated, all the
Minh Nguyen wrote:
> Hi David,
>
> On Sun, Sep 27, 2009 at 12:12 PM, Dr. David Kirkby
> wrote:
>> I've created an update of prereq from 0.3 to 0.4 which does the
>> preliminary checks of the Sage build.
>
> Has anyone ever told you that you're a portability and shell scripting
> guru? From the
William Stein wrote:
> On Sun, Sep 27, 2009 at 12:13 AM, Minh Nguyen wrote:
> FOR supporting 3.4.x:
>
> [ ] It probably would be easy at this point, since it just means
> fixing ratpoints.
>
> [ ] This reminds me of when we dumped support for Cygwin in 2007.
> In retrospect allowing that w
On Sun, Sep 27, 2009 at 12:13 AM, Minh Nguyen wrote:
>
> Hi folks,
>
> Ticket #6580 [1] is meant to have ratpoints build with GCC 3.4.x. The
> Sage build farm uses GCC >= 4.0.1 and ticket #7021 [2] has the updated
> package prereq-0.4 which checks that the target platform has GCC >=
> 4.0.1. With
Well,
hopefully my review comments are helpful!
Cheers,
Georg
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visi
Hi folks,
Ticket #6580 [1] is meant to have ratpoints build with GCC 3.4.x. The
Sage build farm uses GCC >= 4.0.1 and ticket #7021 [2] has the updated
package prereq-0.4 which checks that the target platform has GCC >=
4.0.1. With the updated prereq-0.4 spkg, it invalidates the GCC 3.4.x
requirem
Hi folks,
For your information.
--
Regards
Minh Van Nguyen
-- Forwarded message --
From: Robert Bradshaw
Date: Sun, Sep 27, 2009 at 4:50 PM
Subject: [cython-users] Cython 0.11.3 released
To: cython-us...@googlegroups.com, Cython-dev
We are happy to announce the release of
83 matches
Mail list logo
