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
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
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
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
Okay, I'll install python 2.7 and retry in the morning. Any other
suggestions in the meantime?
Cheers
On Jan 7, 10:19 pm, Dima Pasechnik wrote:
> It appears that you have Python 3 installed on your system, cause I see
> lots of
>
> Making Sage/Python scripts relocatable...
> File "./sage-make_
It appears that you have Python 3 installed on your system, cause I see
lots of
Making Sage/Python scripts relocatable...
File "./sage-make_relative", line 5
print "Making script relocatable"
^SyntaxError: invalid syntax
in your log. In Python 3 print is
Sorry for sounding very ignorant about this process (it's because I
am); but, what other information do you need? What I did was I cd'd
into sage-4.7.2/lib/ and deleted the libppl.* files like Volker
suggested. Then I went back into ~/sage-4.7.2 and make again. My
laptop overheated after about an h
Le 07/01/2012 19:56, ssu a écrit :
Okay. gcc version is 4.6.2 2025. My os is arch bang linux (i686)
with kernel 3.1.5-1-ARCH. What might have gone wrong, should I try it
again?
On Jan 7, 10:27 am, John Cremona wrote:
You need to provide more information about your laptop's operating
sy
Okay. gcc version is 4.6.2 2025. My os is arch bang linux (i686)
with kernel 3.1.5-1-ARCH. What might have gone wrong, should I try it
again?
Thank you for your patience,
Paul
On Jan 7, 10:27 am, John Cremona wrote:
> You need to provide more information about your laptop's operating
> sy
You need to provide more information about your laptop's operating
system, which compiler (version of gcc) you are using, before people
can help. All those error messages show is that the build was not
successful.
John
On 7 January 2012 18:12, ssu wrote:
> Thank you. The build finnished. Howeve
Thank you. The build finnished. However now when I start sage there's
a string of import errors before the 'sage:' prompt appears. None of
the basic sage commands seem to work properly, either. Here's the
complete error:
ImportError Traceback (most recent call
last)
This is yet another one of those cases where setting LD_LIBRARY_PATH bites
us. We compiled our own PPL library, but gcc requires a slightly different
version. A workaround is to delete $SAGE_LOCAL/lib/libppl.* and then run
make again.
--
To post to this group, send an email to sage-devel@goog
19 matches
Mail list logo
