On Thu, May 20, 2010 at 6:27 AM, gerard henry wrote:
> hello all,
> i've just installed the tarball:
> sage-4.4.1-linux-64bit-arch_linux-x86_64-Linux.tar.gz.
> And it fails:
> [he...@octopus ~]$ sage
> --
> | Sage Version 4.4.1, R
Hi all,
I tried "sage -ba" and the build now completes. Sage now starts without
errors! So it looks to me like the patch to module_list.py is needed for
openSUSE 11.2. Thanks, all.
I also ran:
./sage -docbuild all html 2>&1 | tee -a dochtml.log
It also looks like that works fine now, too.
I a
hello all,
i've just installed the tarball:
sage-4.4.1-linux-64bit-arch_linux-x86_64-Linux.tar.gz.
And it fails:
[he...@octopus ~]$ sage
--
| Sage Version 4.4.1, Release Date: 2010-05-02 |
| Type notebook() fo
Thanks Nathan, Mike,
I applied
http://trac.sagemath.org/sage_trac/attachment/ticket/8844/trac_8844-
module_list.patch to $SAGE_ROOT/devel/sage-main/module_list.py.
What do I now need to do to re-build sage without starting from scratch?
"sage -b" and "sage -f sage" seem to "work", but they don't f
Hi all,
OK. I have now run make again, this time with
unset SAGE_CHECK
unset SAGE64
The build apparently completes, but dochtml.log still has much the same error
messages:
---
sphinx-build -b html -d
/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/doctrees/en/numerical_s
On Mon, May 17, 2010 at 4:22 PM, Paul Leopardi
wrote:
> Hi all,
> make clean
> make
>
> does not work the way I expected it to. I expected it to clean out my existing
> build of sage and start again. Instead, "make clean" outputs:
Use "make distclean".
William
>
> echo "Deleted spkg/build"
> D
Hi all,
make clean
make
does not work the way I expected it to. I expected it to clean out my existing
build of sage and start again. Instead, "make clean" outputs:
echo "Deleted spkg/build"
Deleted spkg/build
rm -rf spkg/build
mkdir -p spkg/build
echo "Deleted spkg/archive"
Deleted spkg/archive
Thanks, Jaap,
> From: Jaap Spies
> Mon, 17 May 2010 18:30:23 +0200
>
> Paul Leopardi wrote:
> > Thanks, Georg,
> > I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5,
used
> > tar zcf to creat a replacement spkg, and the make now continues past
> > symmetrica-2.0.p5. The ma
Hi all,
The build on my machine apparently finished. The end of install.log looks
like:
--
[...]
Successfully installed sagetex-2.2.5
Running the test suite.
pdfTeX using libpoppler 3.1415926-1.40.9-2.2 (Web2C 7.5.7)
kpathsea vers
In the makefile for symmetrica, the -lm has to go after all the .o files that
need libm.a or libm.so. This is standard practice for GNU binutils and not a
quirk of OpenSUSE, so I don't see why the build should have worked with any
other Linux distribution (remember that I have exported
SAGE_CHE
Thanks, Georg,
I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5, used
tar zcf to creat a replacement spkg, and the make now continues past
symmetrica-2.0.p5. The make is still running.
I have the following environment variables defined:
SAGE64=yes
SAGE_CHECK=yes
SAGE_ROO
Thanks for the help. I tried again but with
export SAGE64=yes
before running make.
The only difference is that the calls to gcc now include the option -m64.
The warning and error messages are the same.
Best, Paul
--- install.2.log 2010-05-16 15:38:19.0 +1000
+++ install.log 2010-05-
On 05/16/10 07:01 AM, Paul Leopardi wrote:
Hi all,
I am trying to build Sage 4.4.1 from sourece, using gcc 4.4.1 on SUSE 11.2.
So far I have had two failures. I can work around the first, but have no clue
about the second.
Best, Paul
1. Problem with libreadline
Symptom:
[...]/local/lib/libreadli
Hi all,
I am trying to build Sage 4.4.1 from sourece, using gcc 4.4.1 on SUSE 11.2.
So far I have had two failures. I can work around the first, but have no clue
about the second.
Best, Paul
1. Problem with libreadline
Symptom:
[...]/local/lib/libreadline.so.6: undefined symbol: PC
Workaround:
T
Using Sage 4.4.1 (it built fine) on a Sun Blade 2000 (dual 1.2 GHz), I tried to
run 'ptestlong'. I got this failure: (There may be others, I just started the
tests). I've never before run ptestlong, so I don't know how reliable it is on
Solaris. (I've tended to avoid anything parallel in Sage, a
Hi all,
I has updated Live Sage cdrom to Sage-4.4.1.
If you had made a Live Sage system on USB stick as previous thread,
you can download the independent "sage-4.4.1.lzm" and replace the old
sage-4.4.lzm in
%USB%/slax/optional/python/ to update Sage.
CDROM image: http://diffusion.cgu.edu.tw/ft/
Hi,
I've released sage-4.4.1:
http://sage.math.washington.edu/home/wstein/build/release/4.4.1/sage-4.4.1.tar
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this g
On Fri, Apr 30, 2010 at 9:39 PM, Mike Hansen wrote:
> On Fri, Apr 30, 2010 at 9:27 PM, Dima Pasechnik wrote:
>> Seems that this is connected to the reported
>> *** glibc detected *** python: corrupted double-linked list:
>> 0x6140b350 ***
>> troubles.
>
> My guess is that it is indeed
> h
On Fri, Apr 30, 2010 at 9:27 PM, Dima Pasechnik wrote:
> Seems that this is connected to the reported
> *** glibc detected *** python: corrupted double-linked list:
> 0x6140b350 ***
> troubles.
My guess is that it is indeed
http://trac.sagemath.org/sage_trac/ticket/8830 . You can try
ins
I've built sage-4.4.1.alpha2 on ia64 (Skynet's iras), with gcc-4.5.0,
to investigate recently made GAP patches.
It builds, but during the process, as well as during 'make test' I see
lots of
Unhandled SIGSEGV: A segmentation fault occure
Hi folks,
Sage 4.4.1.alpha2 contains two PolyBoRi spkg's:
* polybori-0.6.3-20091028.spkg
* polybori-0.6.4.spkg
I think polybori-0.6.4.spkg is the newer one, so I deleted the other
one from SAGE_ROOT/spkg/standard/. Here's a diff between the
spkg-install of polybori-0.6.3-20091028.spkg and polybo
On Thu, 29 Apr 2010 12:33:04 +
Willem Jan Palenstijn wrote:
> On Thu, Apr 29, 2010 at 10:20:25AM +, Willem Jan Palenstijn wrote:
> > On Thu, Apr 29, 2010 at 07:01:10PM +1000, Minh Nguyen wrote:
> > > Hi folks,
> > >
> > > Sage 4.4.1.alpha2 builds OK on sage.math. I wasn't able to run
> >
On Thu, Apr 29, 2010 at 10:20:25AM +, Willem Jan Palenstijn wrote:
> On Thu, Apr 29, 2010 at 07:01:10PM +1000, Minh Nguyen wrote:
> > Hi folks,
> >
> > Sage 4.4.1.alpha2 builds OK on sage.math. I wasn't able to run
> > doctests on the Sage library. When trying to wrap up a binary for
> > sage.
On Thu, Apr 29, 2010 at 07:01:10PM +1000, Minh Nguyen wrote:
> Hi folks,
>
> Sage 4.4.1.alpha2 builds OK on sage.math. I wasn't able to run
> doctests on the Sage library. When trying to wrap up a binary for
> sage.math, the reason became apparent:
>
> [mv...@sage sage-4.4.1.alpha2]$ ./sage -bdis
Hi folks,
Sage 4.4.1.alpha2 builds OK on sage.math. I wasn't able to run
doctests on the Sage library. When trying to wrap up a binary for
sage.math, the reason became apparent:
[mv...@sage sage-4.4.1.alpha2]$ ./sage -bdist
4.4.1.alpha2-sage.math.washington.edu
Sage works!
*** glibc detected ***
Hi folks,
Sage 4.4.1.alpha2 has a directory that is not under revision control:
[mv...@sage sage-main]$ pwd
/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/devel/sage-main
[mv...@sage sage-main]$ hg status
? doc/en/thematic_tutorials/group_theory.rst
The directory is
SAGE_ROOT/devel/sage-main/doc/en/t
26 matches
Mail list logo
