Greetings! Its just come to my attention that GCL may face some artificially stiff memory requirements at compilation time due to our calling gcc via fork(). I had thought that on most Linux-like systems, fork() used copy on write pages, and required no immediate extra memory. I may be mistaken, and fork() may fail if there is not at least twice the current *virtual* memory available on the system. If so, we should redesign and call gcc via run-process. can anyone please verify this hypothesis?
Take care, -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gcl-devel
