On Tue, 07 Sep 2010 at 12:09PM +0200, Jeroen Demeyer wrote:
> In order to test this thoroughly, extract the tarball and then:
> cd sage-4.6.prealpha4
> make
> env SAGE_CHECK=yes SAGE_TUNE_pari=yes ./sage -f
> pari-2.4.3.svn-12577.p5.spkg
> make ptestlong
Another data point: with the above
On 09/ 9/10 03:32 AM, Tim Daly wrote:
Some of the questions you have about "why lisp" are answered in:
http://channel9.msdn.com/shows/Going+Deep/Expert-to-Expert-Rich-Hickey-and-Brian-Beckman-Inside-Clojure/
which is about Clojure, a more recent lisp although the ideas are
essentially the same i
On 2010-09-08 22:05, Dr. David Kirkby wrote:
> Could you build it in a number of times in a loop and let us know if it
> ever fails.
I built it 100 times (without SAGE_CHECK) and it was successful every time.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe f
There's odd bits code scattered around in Sage that do tests for g95, which is
an old Fortran 95 compiler that in any modern Linux or Unix systems.
According to Wikipedia
http://en.wikipedia.org/wiki/G95
gfortran was forked from g95 in 2003 - i.e. 7 years ago.
I'm not sure at what point gfor
On 09/ 9/10 10:09 AM, Dr. David Kirkby wrote:
There's odd bits code scattered around in Sage that do tests for g95,
which is an old Fortran 95 compiler that in any modern Linux or Unix
systems.
Oops, I mean its an old compiler that you will not find on any modern system.
Since ATLAS is not in
> There's odd bits code scattered around in Sage that do tests for g95, which
> is an old Fortran 95 compiler that in any modern Linux or Unix systems.
>
> According to Wikipedia
>
> http://en.wikipedia.org/wiki/G95
>
> gfortran was forked from g95 in 2003 - i.e. 7 years ago.
>
That doesn't me
On 09/ 9/10 09:53 AM, Jeroen Demeyer wrote:
On 2010-09-08 22:05, Dr. David Kirkby wrote:
Could you build it in a number of times in a loop and let us know if it
ever fails.
I built it 100 times (without SAGE_CHECK) and it was successful every time.
I think given that, and even the person th
Builds ok after all on PPC OS X 10.4 (whew!) - to test would overload
things too much for what I need it for now.
However, I noticed something weird:
Dasher-03:~/Desktop/sage-4.6.prealpha4 student$ ./sage
--
| Sage Version 4.6.pr
On Sep 9, 5:09 am, "Dr. David Kirkby" wrote:
> There's odd bits code scattered around in Sage that do tests for g95, which is
> an old Fortran 95 compiler that in any modern Linux or Unix systems.
>
> According to Wikipedia
>
> http://en.wikipedia.org/wiki/G95
>
> gfortran was forked from g95 in
Does anyone sometimes get weird behavior on Safari when viewing Trac
tickets? None of the formatting comes through at times (now is such a
time, but it's happened for me for months, never long enough to
complain until now). Firefox works fine, as do Chrome and Opera
(didn't try IE). Any ideas?
On Sep 9, 9:19 pm, kcrisman wrote:
> Does anyone sometimes get weird behavior on Safari when viewing Trac
> tickets?
yes, on my old PowerBook G4 I get this with Safari once in a while.
> None of the formatting comes through at times (now is such a
> time, but it's happened for me for months, n
On Sep 9, 9:05 pm, kcrisman wrote:
> On Sep 9, 5:09 am, "Dr. David Kirkby" wrote:
>
>
>
>
>
> > There's odd bits code scattered around in Sage that do tests for g95, which
> > is
> > an old Fortran 95 compiler that in any modern Linux or Unix systems.
>
> > According to Wikipedia
>
> >http://e
On Sep 9, 3:12 am, Peter Jeremy wrote:
> On 2010-Sep-06 21:29:35 +0100, "Dr. David Kirkby"
> wrote:
>
> >I would be very weary of any random number generator that claims to be a good
> >source of random numbers if the output differs by platform or compilation
> >mode.
>
> It depends what you
On 9 September 2010 10:23, François Bissey wrote:
>> There's odd bits code scattered around in Sage that do tests for g95, which
>> is an old Fortran 95 compiler that in any modern Linux or Unix systems.
>>
>> According to Wikipedia
>>
>> http://en.wikipedia.org/wiki/G95
>>
>> gfortran was forked
On Sep 9, 2010, at 3:33 PM, Dima Pasechnik wrote:
> On Sep 9, 9:19 pm, kcrisman wrote:
>> Does anyone sometimes get weird behavior on Safari when viewing Trac
>> tickets?
>
> yes, on my old PowerBook G4 I get this with Safari once in a while.
I saw this just the other day on Omniweb (which proba
Hi Dima!
On Sep 9, 2:44 pm, Dima Pasechnik wrote:
>...
> Nobody seems to be willing to review the ticket, however, as if the
> problem got resolved in a way that escapes me.
The problem for my package did indeed resolve, due to
current_randstate().set_seed_gap(). But of course it should better b
> > > William said here
>
> > >http://groups.google.com/group/sage-devel/browse_thread/thread/1b6235...
>
> > > "Probably the only platforms that get g95 are older OS X."
>
> > It seems like PowerPC gets it.
>
> Well, I run MacOSX 10.5 on my PPC (G4), and I have gfortran.
Can you give me a command
> Unsurprisingly, the R project has a site (http://r.research.att.com/
> tools/) with links to lots of Fortran compilers, including apparently
> one gfortran one which would work on 10.4 (?).
Though apparently one then also needs to download a newer-built Xcode
- a custom one which has gcc 4.2 (a
>
> However, I've had no success running RJF's code. I would have thought the ANSI
> Common Lisp would have covered how commands are loaded, but I am told that is
> not so. If Richard could suggest how his code might be modified to run with
> ECL,
> then I'd like to give it a quick try and post m
Okay, I finally figured out how to check this - I had to run the
binary directly, the scripts didn't work because of the way they're
used (since gfortran isn't in my PATH, of course):
G95 (GCC 4.0.3 (g95 0.91!) Jun 4 2007)
Dima, can you look at your $SAGE_LOCAL/bin/sage_fortran and tell us
what i
On 9 September 2010 15:33, kcrisman wrote:
>> > > William said here
>>
>> > >http://groups.google.com/group/sage-devel/browse_thread/thread/1b6235...
>>
>> > > "Probably the only platforms that get g95 are older OS X."
>>
>> > It seems like PowerPC gets it.
>>
>> Well, I run MacOSX 10.5 on my PPC
Dear sage-devel,
Sage is very slow. I discovered this (again) while trying to write a
prototype of an algorithm for computing zeta functions of projective
varieties. I need to multiply lots of polynomials and matrices over
finite rings, and frequently move coefficients between polynomials
###
>
> 2) The next question is whether we should remove *all* code in Sage
> that make a distinction between g95 and gfortran. I propose that Sage
> still allows one to specify a Fortran compiler with SAGE_FORTRAN, but
> if that's not set, it jus
On Thu, Sep 9, 2010 at 9:24 AM, David Harvey wrote:
> Dear sage-devel,
>
> Sage is very slow. I discovered this (again) while trying to write a
> prototype of an algorithm for computing zeta functions of projective
> varieties. I need to multiply lots of polynomials and matrices over finite
> ring
I didn't build sage on my G4 since 4.3.4, and there gfortran points to
something I got from fink.
So I must have built Sage using fink's gfortran, built against
gcc-4.3.4 ? Hmm.
OK, let me try the current release and see if I get anywhere.
(It will take a while...)
Dima
On Sep 9, 11:20 pm, kcrism
On 2010-09-09 14:48, kcrisman wrote:
> sage:
> Exiting Sage (CPU time 0m0.28s, Wall time 0m3.25s).
> Exiting spawned GP/PARI interpreter process.
>
> Note the last line. This is repeatable. Do we really want this? We
> do get an exit of a spawned GAP process when one moves Sage to a new
> locat
On 9/9/10 11:24 AM, David Harvey wrote:
Maybe I can be the first to #1 if I keep going!
+1 to you opening up 118 tickets and posting patches to them!
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-deve
On Sep 9, 12:40 pm, Jeroen Demeyer wrote:
> On 2010-09-09 14:48, kcrisman wrote:> sage:
> > Exiting Sage (CPU time 0m0.28s, Wall time 0m3.25s).
> > Exiting spawned GP/PARI interpreter process.
>
> > Note the last line. This is repeatable. Do we really want this? We
> > do get an exit of a spa
On Sep 9, 12:31 pm, Dima Pasechnik wrote:
> I didn't build sage on my G4 since 4.3.4, and there gfortran points to
> something I got from fink.
> So I must have built Sage using fink's gfortran, built against
> gcc-4.3.4 ? Hmm.
> OK, let me try the current release and see if I get anywhere.
> (I
Hi,
built successful and almost all test passed (ptestlong) on AMD Phenom
X4 II, Fedora 13
one test failed, this is related to
http://trac.sagemath.org/sage_trac/ticket/9847
Georg
On Sep 7, 12:09 pm, Jeroen Demeyer wrote:
> Hello sage-devel,
>
> As far as we know, there are no more remaini
On Sep 9, 7:00 pm, kcrisman wrote:
> On Sep 9, 12:40 pm, Jeroen Demeyer wrote:
>
> > On 2010-09-09 14:48, kcrisman wrote:> sage:
> > > Exiting Sage (CPU time 0m0.28s, Wall time 0m3.25s).
> > > Exiting spawned GP/PARI interpreter process.
>
> > > Note the last line. This is repeatable. Do we r
Currently, installing packages on a Sage that has been moved from its
original build location is seriously broken. The problem is that the
pkgconfig files (which many spkgs use to set up the include paths) are
not updated to the new location.
There is a patch at #9210 that fixes this. It nee
On 09/ 9/10 09:07 PM, Jason Grout wrote:
Currently, installing packages on a Sage that has been moved from its
original build location is seriously broken. The problem is that the
pkgconfig files (which many spkgs use to set up the include paths) are
not updated to the new location.
There is a p
On 9/9/10 5:51 PM, Dr. David Kirkby wrote:
On 09/ 9/10 09:07 PM, Jason Grout wrote:
Currently, installing packages on a Sage that has been moved from its
original build location is seriously broken. The problem is that the
pkgconfig files (which many spkgs use to set up the include paths) are
no
On 9 sep, 18:24, David Harvey wrote:
> Sage is very slow. I discovered this (again) while trying to write a
> prototype of an algorithm for computing zeta functions of projective
> varieties. I need to multiply lots of polynomials and matrices over
> finite rings, and frequently move coeffic
On Sep 9, 7:44 pm, cousteau wrote:
> On 9 sep, 18:24, David Harvey wrote:
>
> > Sage is very slow. I discovered this (again) while trying to write a
> > prototype of an algorithm for computing zeta functions of projective
> > varieties. I need to multiply lots of polynomials and matrices over
There are some implemented coercion maps already (see
sage.rings.finite_rings.integer_mod.Integer_to_IntegerMod). Many of these
tickets can be solved by writing optimized coercion and conversion morphisms
and including appropriate section() functions on some of them. See the
patch at #9814, thoug
Hi,
It seems you have a permission problem. Please try running:
$ sudo chown :users ~/sage/sage-4.5.2 -R
$ chmod ug+rwX ~/sage/sage-4.5.2 -R
And see if that fixes things.
On Thu, Sep 9, 2010 at 2:43 PM, Enrico wrote:
> Hi sage-devel, I'm having a problem with sagenb and it told me to post
> he
Thanks Tim, I tried that but I still get the import error. However if
I use this shell:
cd '/home/me/sage/sage-4.5.2/spkg/build/sagenb-0.8.2' && '/home/me/
sage/sage-4.5.2/sage' -sh
then I get a working notebook.
I made a .bash_profile:
SAGE_ROOT="/home/me/sage/sage-4.5.2"
PATH="$PATH:$SAGE_ROOT:$
You don't need to set those environment variables in your profile. The
sage binary sets those automatically.
On Fri, Sep 10, 2010 at 10:36 AM, Enrico wrote:
> Thanks Tim, I tried that but I still get the import error. However if
> I use this shell:
> cd '/home/me/sage/sage-4.5.2/spkg/build/sagenb
After some trial and error, I came across
http://r.research.att.com/tools/#gcc42
that describes a process of building gfortran using Xcode gcc-4.2
(available since Xcode release
3.1.1, at least --- current is Xcode 3.1.4 released Sept 2009).
This will work on both PPC and Intel Macs running at MacO
41 matches
Mail list logo
