On Tuesday, 18 June 2013 06:39:20 UTC+2, Volker Braun wrote: > > I've built Sage on Cygwin today in a 4GB i386 virtual machine. The plus > side: It builds without any major hitches. Jean-Pierre Flori and others did > a lot of work to clean this up.
what is the Windows version you are using? Is it a 32-bit? I've had a lot of trouble with this one, and much less with a 64-bit (I'm not talking about about 32 vs 64-bit Cygwin). It probably has to do with the amount of space one has to allocate for all the dlls. > > But I'm still unable to consistently get the documentation to build, I > often get the dreaded "address space needed by <some Sage dll> is already > occupied" error which is due to the fundamental limitation of the fork > emulation. In fact, sometimes the documentation builds successfully and > sometimes it does not, depending on process space memory layout I guess. > This is really random, and I can't get it to consistently work with any > amount of rebasing. I've seen instances where docbuild works once and then > fails immediately afterwards when I repeat it, without me having changed > anything between the runs. > > This is not just about the documentation, this step is just particularly > critical since everything will be imported during the docbuild step. So if > any shared library has a problem, it will likely be encountered during the > docbuild. Since Sage is probably the largest number of shared libraries in > Cygwin ever, it is conceivable that this is a fundamental limitation (at > least unless 64-bit cygwin works). Any thoughts? > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
