Update:
Since my last update;
The Atlas problem seemed to have been fixed with the atlas-3.8.3.p17
spkg, however I ran into more trouble later with matplotlib-1.0.0
and that sent me off on a course of enquiry that led me to try
building
each component separately; BLAS, NUMPY, PYTHON, ATLAS, etc.
At one point I gave up and downloaded a pre-built binary.
I got back to building on friday and I am HAPPY to announce that
I have successfully built and tested SAGE in the Linux partition AND
in a virtual box under Windows Vista.
This is with the original atlas-3.8.3.p16 from the tarball.
This is probably documented somewhere and in any case I should
have taken it as implicit that one needs to be ROOT to do the build.
{perhaps in formal terms I should say one needs to have root acting
on one's behalf, i.e. $sudo su on Ububtu/Debian}
That was sufficient on the standalone Linux partition.
In the Virtual box it SEEMS to be necessary to give the virtual
machine
more than 1 Gig of memory.
Although I haven't found the limit 2,961 Meg has worked here.
Virtual Box would not allow me to devote more than 75% of the physical
machine's memory and I only have 4 Gig.
Also it is not necessary to disable CPU throttling in the virtual
machine.
I can speculate why, but Atlas reports that it cannot detect
throttling.
On Nov 6, 10:45 am, RegB <2regburg...@earthlink.net> wrote:
> I get confused with the directions about running in virtual box (-:
> I think it should be OK and very possible to create virtual
> machines, say within virtual box within Windows Vista and install
> Linux in those VMs , then go ahead and install Sage on the Linux.
> i.e. (Windows Vista (Virtual Box(UBUNTU10.10(Sage))))
> Now the Linux doesn't have anything LIKE a wall clock, so I
> would have to ASSUME that Atlas would blow itself up
> on the timing, other than that I see no GOOD reason to not put
> ANY pre-built sage in a virtual machine within Virtual Box.
> I may try that if/when I get a good build underUBUNTU10.10
>
> SO FAR my build with atlas-3.8.3.p17 is running successfully,
> it has gone WAY past the Atlas install.
>
> On Nov 6, 12:36 am, Andrey Novoseltsev <novos...@gmail.com> wrote:
>
> > This may be related:
>
> > I also regularly (although not deterministically) have troubles with
> > ATLAS on a Turion x2 notebook. I has 4Gb RAM, but I am runningUbuntu
> > 10.4 in VirtualBox with 1.5Gb and one CPU core accessible to it. It
> > always takes forever to build ATLAS on it and often it crashes. Since
> > I mostly work on other computers anyway, I don't get too concerned and
> > just repeat make or sage -upgrade when it happens, usually it
> > helps ;-) It also seems to me that mistakes happen only if I DON'T use
> > the computer at all (including host OS) while the build goes, but I am
> > not sure.
>
> > Thank you,
> > Andrey
--
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://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
