On Nov 10, 12:48 am, John Voight <[EMAIL PROTECTED]> wrote:
> I tried to sage -upgrade my 2.8.9 this evening on an Ubuntu x686, and
> I got:
>
> Building sage/matrix/misc.c because it depends on sage/matrix/
> misc.pyx.
> touch sage/matrix/misc.pyx; cython --embed-positions --incref-local-
> bin
I just downloaded a new tarball from sage.math. JV
--~--~-~--~~~---~--~~
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.co
I tried to sage -upgrade my 2.8.9 this evening on an Ubuntu x686, and
I got:
Building sage/matrix/misc.c because it depends on sage/matrix/
misc.pyx.
touch sage/matrix/misc.pyx; cython --embed-positions --incref-local-
binop -I/home/kostadm/sage/devel/sage-main -o sage/matrix/misc.c sage/
matrix/
On Nov 9, 2007 4:49 AM, Joshua Kantor <[EMAIL PROTECTED]> wrote:
> This is something which has confused me in the past.
> The issue is that there are two shared object libraries with the exact
> same name. If we compile with -L$SAGE_LOCAL/lib
> are we guaranteed that this will be searched before /
This is something which has confused me in the past.
The issue is that there are two shared object libraries with the exact
same name. If we compile with -L$SAGE_LOCAL/lib
are we guaranteed that this will be searched before /usr/lib at
runtime.
Josh
On Nov 8, 6:22 pm, mabshoff <[EMAIL PROTECT
On Nov 9, 3:14 am, Joshua Kantor <[EMAIL PROTECTED]> wrote:
Hi Josh,
> Yeah. the missing symbol is because its linking against libblas in /
> usr/lib, which was compiled with some other probably older fortran
> (why oh why can't all the fortrans get along).
>
> I'm curious about what people
Yeah. the missing symbol is because its linking against libblas in /
usr/lib, which was compiled with some other probably older fortran
(why oh why can't all the fortrans get along).
I'm curious about what people think is a good solution here.
If they have a libblas in /usr/lib thats broken lik
On Nov 8, 9:50 pm, Kate <[EMAIL PROTECTED]> wrote:
> Michael,
>
> sage -t devel/sage-main/sage/numerical/test.py
> **
> File "test.py", line 4:
> : from cvxopt.base import *
> Exception raised:
> Traceback (most rece
On Nov 8, 9:50 pm, Kate <[EMAIL PROTECTED]> wrote:
> Michael,
Kate,
>
> Much thanks for the link to Josh's update of cvxopt.spkg.
No problem.
>
> With that fix, I now can compile on all the architectures
> I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux.
>
> The next st
Michael,
Much thanks for the link to Josh's update of cvxopt.spkg.
With that fix, I now can compile on all the architectures
I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux.
The next step is to run 'make check', which I have done.
Sadly, only x86-Linux passes all the test
William,
I am confused about why you forwarded my build report to sage-devel.
According to the "About this group"
sage-support: This email list is to report possible bugs in SAGE or
to post a
support-related issue.
sage-devel: This email list is for discussion of SAGE development
issues.
I wa
On Nov 8, 2007 3:12 PM, Kate <[EMAIL PROTECTED]> wrote:
> I am confused about why you forwarded my build report to sage-devel.
> According to the "About this group"
I forwarded your email because I know for a fact that several of the
people likely to fix the problems you reported only subscribe t
On Nov 8, 3:59 pm, Kate <[EMAIL PROTECTED]> wrote:
> Michael,
Hello Kate,
>
> I have tried
>
> http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p...
>
> and can report that it builds on my x86_64-Linux box.
Great. I will make sure the updated spkg goes into 2.9 or whatever
Michael,
I have tried
http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p0.spkg
and can report that it builds on my x86_64-Linux box. The build is
now
stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for
x86-Linux and ia64-Linux.
Kate
On Nov 7, 6:16 pm, mab
About the cvxopt problem
Now the package checks sage_fortran -v and uses a setup.py that links
against f95
if you have g95 and a setup.py that links against gfortran otherwise.
(this package is in my spkgs cvxopt-0.8.2.p5.spkg)
I have tested it with both g95 and gfortran.
Josh
On Nov 7, 3:
On Nov 7, 8:08 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> This should really be sent to sage-devel, so I'm forwarding it there.
>
> -- Forwarded message --
> From: William Stein <[EMAIL PROTECTED]>
> Date: Nov 7, 2007 11:07 AM
> Subject: Re: [sage-support] sage-2.8.12 build
Ok, then I'll look at sage_fortran --version.
On Nov 7, 1:00 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Nov 7, 2007 12:52 PM, Joshua Kantor <[EMAIL PROTECTED]> wrote:
>
>
>
> > Thats expected, since the fix I made was for g95 builds and it worked
> > by linking in f95, which won't be a
On Nov 7, 2007 12:52 PM, Joshua Kantor <[EMAIL PROTECTED]> wrote:
>
> Thats expected, since the fix I made was for g95 builds and it worked
> by linking in f95, which won't be around using gfortran. Should be
> easy to add a test for gfortran.
>
> I was going to test whether or not $SAGE_FORTRAN w
Thats expected, since the fix I made was for g95 builds and it worked
by linking in f95, which won't be around using gfortran. Should be
easy to add a test for gfortran.
I was going to test whether or not $SAGE_FORTRAN was set and use an
appropriate setup.py depending on whether or not this is tr
19 matches
Mail list logo
