I had some success that I thought I would share: I temporarily disabled SINGLE_HOST, and that worked fine. I also updated to gcc 4.4.1 and was able to build everything with SINGLE_HOST enabled. Thanks for the help, Steve On Sun, Aug 30, 2009 at 10:54 PM, Frederick LeMaster<fred.lemaster@gmail.com> wrote:
You could always pass the option -cc-options "-U___SINGLE_HOST", but there'll be a performance hit in the resulting code. gcc has issues with very large function definitions, like the ones gambit produced when --enable-single-host is in effect.
On Sun, Aug 30, 2009 at 9:21 PM, Steve Huffman<steve.huffman@gmail.com> wrote:
I'm running OS X with 4 gigs of ram. I notice the cc process that is spawned uses about 3.5 gigs before it dies. That seems a bit excessive, no?