Hi All,
I'm attempting to compile Black Hole on Gambit 4.5.1. I've installed BH from Git. I ran modules-compile!, and each of the standard BH modules compiled successfully, except for srfi-13, which fails because it runs out of memory.
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?
(modules-compile! (modules-in-dir "~~/lib/modules/std") #t)
Compiling 1 modules "/usr/local/Gambit-C/lib/modules/std/srfi/13.scm" (1/1) cc1(209) malloc: *** mmap(size=97247232) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug
cc1: out of memory allocating 97245440 bytes after a total of 0 bytes Warning: Compilation failed: C compilation or link failed while compiling "/usr/local/Gambit-C/lib/modules/std/srfi/13.scm"
Thanks for any help,
Steve
Afficher les réponses par date
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 Huffmansteve.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?
Hallo,
On 8/31/09, 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 Huffmansteve.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?
Some GCC versions have trouble with code generated by Gambit-C unless one uses -fno-move-loop-invariants.
Cheers,
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 LeMasterfred.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 Huffmansteve.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?