Reporting (a little late) a successful build of 2.7 followed by a good
upgrade to 2.7.2.1 on Feisty Fawn Core2Duo 1GB.
I noticed my last name was misspelled in the credits...
It is D. Raymer instead of 'Ramier'.
-Dorian
On 7/20/07, William Stein <[EMAIL PROTECTED]> wrote:
>
>
> On 7/20/07, Pabl
On 7/22/07, Hamptonio <[EMAIL PROTECTED]> wrote:
>
> Building from scratch on a ppc laptop, I run aground when it gets to
> lapack. I already had a gfortran installed which may be the problem.
It's almost certainly caused by that. Please use a binary or wait
for sage-2.7.1, which will be releas
God, bedtime for me. Sorry the patch includes a conflicting diff that
can be ignored (keep the sage-2.7 version) for revision:
http://www.ms.uky.edu/~jack/sage/hg/sage-permgps-bugfix/rev/b37a82329af1
(add dollars to documentation).
The diffs:
http://www.ms.uky.edu/~jack/sage/hg/sage-permgps-bugf
Yup, that works perfectly. Sorry, I thought I had already checked
this since I ran ~/sage/sage-2.6/local/bin/hg, but that just runs the
debian supplied copy of mercurial anyways.
Using the sage -hg version from the 64bit linux binary install,
everything worked fine. The permutation patches at
h
> Aha! I am new at python and misunderstood how hg was working. All the
> file "hg" does is import stuff from python, so it doesn't matter which
> copy of hg I use, it matters which copy of python. The debian
> supplied hg is broken, but the sage-2.6 version of hg works fine.
>
> Sorry for miside
Aha! I am new at python and misunderstood how hg was working. All the
file "hg" does is import stuff from python, so it doesn't matter which
copy of hg I use, it matters which copy of python. The debian
supplied hg is broken, but the sage-2.6 version of hg works fine.
Sorry for misidentifying th
On 7/21/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
> This appears to be an amd64 related bug.
>
> The 64bit version:
>
> $ wget -q http://www.sagemath.org/dist/src/sage-2.7.tar
> $ md5sum sage-2.7.tar
> 31209ee51f2aace7e9df1a33e46fa89d sage-2.7.tar
> $ tar -xf sage-2.7.tar
> $ cd sage-2.7
> $ ta
This appears to be an amd64 related bug.
The 64bit version:
$ wget -q http://www.sagemath.org/dist/src/sage-2.7.tar
$ md5sum sage-2.7.tar
31209ee51f2aace7e9df1a33e46fa89d sage-2.7.tar
$ tar -xf sage-2.7.tar
$ cd sage-2.7
$ tar -xf spkg/standard/sage-2.7.spkg
$ md5sum spkg/standard/sage-2.7.spkg
That is very strange. My md5sum is the same.
$ md5sum spkg/standard/sage-2.7.spkg
07de6836d75b3fab84555d130f7d5f38 spkg/standard/sage-2.7.spkg
$
The error occurs with debian's hg, sage-2.7's hg, and even sage 2.6's
hg:
$ ~/sage/sage-2.6/local/bin/hg up
abort: 00changelog.i: no node
ec597fe01f
On 7/21/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
>
> The corruption only shows up on a few critical hg commands. Here is a
> log, with ~/sage/sage-2.7/ a fresh install from sage-2.7.tar
>
> $ cd ~/sage/sage-2.7/devel/
> $ tar -xf ../spkg/standard/sage-2.7.spkg
> $ cd sage-2.7
> $ hg verify
> c
The corruption only shows up on a few critical hg commands. Here is a
log, with ~/sage/sage-2.7/ a fresh install from sage-2.7.tar
$ cd ~/sage/sage-2.7/devel/
$ tar -xf ../spkg/standard/sage-2.7.spkg
$ cd sage-2.7
$ hg verify
checking changesets
checking manifests
crosschecking files in changese
On 7/20/07, Pablo De Napoli <[EMAIL PROTECTED]> wrote:
> Concerning (2)
>
> I think that if a gfortran it is already installed in the system, it
> would be reasonable to use rather than downloading a binary.
Issues:
(1) If it's gfortran 3.x then it will fail miserably at building
certain compon
On 7/20/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
>
> The mercurial repository contained in this tar file is corrupted
> making it impossible (for me at least) to resubmit my patches.
Could you please elaborate on why you think the hg repository
in sage-2.7.spkg is corrupted?I'd really like
Concerning (2)
I think that if a gfortran it is already installed in the system, it
would be reasonable to use rather than downloading a binary.(gfortran
is in fact, a standard part of gcc, if gcc from the host system is
used for compiling the parts of sage writen in C, why not doing the
same wit
There are two levels of problems
1. We can't include 64 bit compilers because we have no binaries that
work for them.
2. The ar extracting hack is because we are tricking numpy's
distutils into doing what we want.
(More detailed explanation: Numpy's distutils has python classes for
different
Workaround for those who want to get a little further:
tar -xf sage-2.7.tar
cd sage-2.7
mkdir -p spkg/installed
touch spkg/installed/f2c-1
touch spkg/installed/cvxopt-0.8.2
touch spkg/installed/gfortran-20070719
Now ensure that you have a symlink to g77 in your path called
"gfortran"
make
On Ju
16 matches
Mail list logo
