Okay I finnished the build and sage seems to be running smoothly now!
Thank you guys, and Volker for your advice. Hopefully I won't be back
to report any problems in the near future.
Paul
On Jan 8, 6:59 pm, Volker Braun wrote:
> If you had waited long enough then I'm pretty sure you would have a
If you had waited long enough then I'm pretty sure you would have a
finished Sage install by now. Obviously without the documentation, because
your TexLive install lacks latex.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
Whoops, TexLive is what I have, right.
It's giving a string of messages all of which looks like:
WARNING: display latex u'n': latex exited with error:
[stderr]
kpathsea: Running mktexfmt latex.fmt
[stdout]
This is pdfTeX, Verion 3.1415926-2.3-1.40.12 (Tex Life 2012/dev/Arch
Linux) restricted \w
You probably have TexLive. Not all errors are fatal. Post the relevant part
of your log.
--
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, visit this group at http://g
So if I put it in ~/bin should it look like
#!/bin/sh
LD_LIBRARY_PATH=~/bin
export LD_LIBRARY_PATH
/usr/bin/gcc "$@"
?
I tried making again and install.log kept saying it could not find a
Latex format file. I have liveTex installed. But the documentation
says it's not even a prereq. for building
Bahh, disappointed (-:
Using 'make ptestlong' I just got;
=
sage -t --long -force_lib devel/sage/sage/modular/modform/
cuspidal_submodule.py
[7.3 s]
sage -t --long -force_lib devel/sage/sage/modular/modform/element.
On Jan 7, 5:39 am, John Cremona wrote:
> (24 hours later)
>
> Successfully built 4.8.alpha6
> withhttp://sage.math.washington.edu/home/palmieri/SPKG/readline-6.2.p3.spkg
> put into spkg/standard before starting to build. All long tests pass
> and there is no warning about readline, and history
It ran straight through here.
DETAILS: Toshiba Satellite P775 laptop, i7, 8 Gig Ram, Windows 7 Home
Premium,
Virtual Box allowed 4 Gig Ram and 95% of available processor(s), no
attempt made
to "throttle" the host machine, or the guest.
Almost 3 hours, but from the size of the Atlas
log file 15.7 M
Call it gcc and save it in a directory under your home directory (say,
~/bin). Then make sure that ~/bin is in $PATH before /usr/bin
--
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
Fo
#9992 just prints an erroneous error message. While annoying, it should not
prevent you from building Sage.
--
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, visit thi
On 31 December 2011 14:53, Jeroen Demeyer wrote:
> I have made an unofficial sage-5.0.prealpha0 release. This includes
> various high-profile tickets which will hopefully be merged in the
> sage-5.0 release. The flask notebook is not included yet, as it is not
> quite ready to be merged yet. Se
Volker,
Sage 4.7.2 simply will not build if you have Python 3 installed (as default
Python) on the system.
He was hit by #9992 this way.
--
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.c
Call it gcc or gcc.sh? Also, save it in the /usr/bin under the root
directory or somewhere else?
On Jan 8, 5:48 am, Volker Braun wrote:
> Sage comes with its own python, but that apparently was not installed. You
> really should compile from scratch again. You don't need to install any
> particul
Sage comes with its own python, but that apparently was not installed. You
really should compile from scratch again. You don't need to install any
particular system Python version, it will not be used if you do.
Since the problem was with the PPL library conflict, your best best is to
put a "gc
While another thread has folks thinking about graph automorphisms,
here is another one. Historically, graph vertices were integers
beginning at zero. Permutation groups in GAP have symbols beginning
with one.
The scheme employed is to "promote" vertex zero to the final symbol of
the permutation
This is in fact fixed in Sage 4.8.alpha0 (see
http://trac.sagemath.org/sage_trac/ticket/9992).
You may instead just grab a recent 4.8.alpha
(see https://groups.google.com/forum/#!forum/sage-release)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
16 matches
Mail list logo
