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(UBUNTU 10.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 under UBUNTU 10.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 running Ubuntu > 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
