From: Jonathan B. <jbr...@ea...> - 2004-12-04 15:54:10
|
On Sat, 2004-12-04 at 12:44 +0000, Sanjoy Mahajan wrote: > I'm using 'visual-3.0-20040722.tar.gz'. > > The config.log and the resulting top-level Makefile claim the visual > version is 2.9.7, I think because the 'configure' script has these > lines: > > PACKAGE_VERSION='2.9.7' > PACKAGE_STRING='Visual Python 2.9.7' > > Should the version become 3.0.0? > A few updates for the 'INSTALL.txt': > These things have been fixed in later releases, as well as a few other bugs. 3.0.3 was released to the Sourceforge page yesterday. > I couldn't compile visual on my 96MB Pentium (586) laptop -- the g++ > compile of 'cvisualmodule.cpp' consumed over 150MB of virtual memory > (c++ is an absurd language)! The cc1plus process got about 2% of the > CPU time while swapping like mad. I then compiled everything on a > nearby workstation with more memory, but is there any way to reduce > the memory consumption? > > -Sanjoy There is, but only at the cost of even longer total compile times. I have targeted 256MB of ram as the minimum for building Visual; the runtime requirement is much lower. If a packaging expert provided us with an up to date debian/ directory I would be more than happy to provide a prebuilt .deb for download. -Jonathan |