Thanks,
So it seems that there is no (easy or otherwise) way to build from
latest development tree, only from the last "stable" source tarball.
That's what I was hoping for.
On 9 abr, 18:15, Robert Bradshaw <rober...@math.washington.edu> wrote:
> On Apr 9, 2009, at 7:41 AM, Flavio Coelho wrote:
>
>
>
> > Hi, I cloned Sage from the mercrial repository (hg.sagemath.org) but
> > found no building instructions.
>
> > I want to build it inplace. The install script complains that I must
> > provide a sage root and if I give the current directory, '.', it spits
> > back the following traceback:
>
> > Traceback (most recent call last):
> > File "setup.py", line 14, in <module>
> > from module_list import ext_modules
> > File "/home/fccoelho/Downloads/sage-main/module_list.py", line 29,
> > in <module>
> > elif os.path.exists('%s/lib/libatlas.so'%os.environ
> > ['SAGE_LOCAL']):
> > File "/usr/lib/python2.6/UserDict.py", line 22, in __getitem__
> > raise KeyError(key)
> > KeyError: 'SAGE_LOCAL'
>
> > any help is appreciated.
>
> Sage consists of many mercurial repositories, as well as much code
> that isn't under (our) revision control (e.g. upstream packages).
>
> To build Sage from scratch you need to do is download the source at
> http://www.sagemath.org/download-source.html, unpack the tarball,
> and type make inside of it. Then wait three hours or so. When you
> have a working Sage, type sage -clone branch_name to make a clone of
> the core Sage library code (which sits inside of $SAGE_ROOT/devel,
> where $SAGE_ROOT is the path of the top-level folder). You can then
> edit this and type "sage -b" to rebuild and test your changes.
>
> - Robert
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
