I had (what appeared to me to be) same/similar problems with UBUNTU
11.04
I had NOT attempted to install flask.
The "sage -fhttp://users.aims.ac.za/~jan/python-2.6.4.p10.spkg";
appeared to resolve that,
but I had to re-build docs to get the help and the tutorial up.
I run the plot3d examples as a c
On 13 Maj, 11:59, Jan Groenewald wrote:
>
> The last command there is sage -br, and it perhaps rebuilt the p9 spkg?
>
> Try just do again
>
> sage -f http://users.aims.ac.za/~jan/python-2.6.4.p10.spkg
>
It helped! Thanks. :)
I don't really get how, since I had removed the p9 spkg from spkg/
Hi
On Thu, May 12, 2011 at 09:28:38AM -0700, Lilavati wrote:
> On 24 Kwi, 15:26, pipedream wrote:
> > We expect below spkg to be in sage 4.7.1. In the meantime, if you
> > runUbuntu11.04(Natty)
> > and stable sage 4.6.2, you can replace SAGE_ROOT/spkg/standard/
> > python-2.6.4.p9.spkg
> > with
On 24 Kwi, 15:26, pipedream wrote:
> We expect below spkg to be in sage 4.7.1. In the meantime, if you
> runUbuntu11.04(Natty)
> and stable sage 4.6.2, you can replace SAGE_ROOT/spkg/standard/
> python-2.6.4.p9.spkg
> with this:
>
> http://users.aims.ac.za/~jan/python-2.6.4.p10.spkg
>
I did th
We expect below spkg to be in sage 4.7.1. In the meantime, if you run
Ubuntu 11.04 (Natty)
and stable sage 4.6.2, you can replace SAGE_ROOT/spkg/standard/
python-2.6.4.p9.spkg
with this:
http://users.aims.ac.za/~jan/python-2.6.4.p10.spkg
On Apr 23, 5:43 pm, pipedream wrote:
> This is nowhttp:/
This is now http://trac.sagemath.org/sage_trac/ticket/11243
Testing and reviewing welcome.
--
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://
On Sun, 17 Apr 2011 at 08:27AM +0100, David Kirkby wrote:
> Can you look spkg/logs/python-2.6.4.p9 and see if you can find a
> section like this:
>
> Failed to find the necessary bits to build these modules:
> _bsddb bsddb185 gdbm
> linuxaudiodev ossaudiodev
> To find t
On 04/17/11 10:28 AM, Jan Groenewald wrote:
Hi Dave
On Sun, Apr 17, 2011 at 09:42:32AM +0100, David Kirkby wrote:
OK, its clear Python failed to build the crypt module. I assume this
means it found the bits to build it, but was unable to.
Full logs at
http://users.aims.ac.za/~jan/sage/instal
Hi Dave
On Sun, Apr 17, 2011 at 09:42:32AM +0100, David Kirkby wrote:
> OK, its clear Python failed to build the crypt module. I assume this
> means it found the bits to build it, but was unable to.
>
> > Full logs at
> > http://users.aims.ac.za/~jan/sage/install.log-sage4.6.2-ubuntu11.04-amd64-
On 17 April 2011 09:23, Jan Groenewald wrote:
> Hi
>
> On Sun, Apr 17, 2011 at 08:27:55AM +0100, David Kirkby wrote:
>> >> *** WARNING: renaming "crypt" since importing it failed:
>> >> build/lib.linux-x86_64-2.6/crypt.so: undefined symbol: crypt
>>
>> Can you look spkg/logs/python-2.6.4.p9 and s
Hi
On Sun, Apr 17, 2011 at 08:27:55AM +0100, David Kirkby wrote:
> >> *** WARNING: renaming "crypt" since importing it failed:
> >> build/lib.linux-x86_64-2.6/crypt.so: undefined symbol: crypt
>
> Can you look spkg/logs/python-2.6.4.p9 and see if you can find a
> section like this:
> Failed to f
On 16 April 2011 08:50, pipedream wrote:
> Hi
>
> From an early alpha,
>
> 1. during build
>> *** WARNING: renaming "crypt" since importing it failed:
>> build/lib.linux-x86_64-2.6/crypt.so: undefined symbol: crypt
Can you look spkg/logs/python-2.6.4.p9 and see if you can find a
section like th
Hi
>From an early alpha,
1. during build
> *** WARNING: renaming "crypt" since importing it failed:
> build/lib.linux-x86_64-2.6/crypt.so: undefined symbol: crypt
2. starting sage
> jan@mamadou-laptop:/usr/local/src/sage-4.6.2$ sage
> ImportError: No module named crypt
This problem continues o
Hi
>From an early alpha,
1. during build
> *** WARNING: renaming "crypt" since importing it failed:
> build/lib.linux-x86_64-2.6/crypt.so: undefined symbol: crypt
2. starting sage
> jan@mamadou-laptop:/usr/local/src/sage-4.6.2$ sage
> ImportError: No module named crypt
This problem continues o
14 matches
Mail list logo