Building 0.4.3 via nave on Ubuntu 10.04 - g++ issue

[James Cooper]

Hi there,

Not sure if this is a nave or node related issue, so apologies if I shouldn't post this here.

Last night I tried using nave for the first time to build the latest release version (0.4.3) on an Ubuntu 10.04 VM on my mac.  It failed with some g++ errors.  I tried 0.4.2 and 0.4.1 and got similar issues.  The exact file that the build fails on varies.  

Moments ago I grabbed the latest node sources from github.  This built cleanly on the same VM using a standard: ./configure;  make    sequence.

It looks like nave passes different switches to g++   I'm guessing that's the issue.  

Here's what one of the nave compile lines looks like:

g++ -o obj/debug/checks.o -c -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -g -O0 -ansi -fno-rtti -fno-exceptions -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -g -O0 -ansi -DV8_TARGET_ARCH_X64 -DENABLE_DISASSEMBLER -DDEBUG -DENABLE_VMSTATE_TRACKING -DENABLE_LOGGING_AND_PROFILING -DENABLE_DEBUGGER_SUPPORT -DV8_ENABLE_CHECKS -DOBJECT_PRINT -I/home/james/.nave/src/0.4.3/deps/v8/src /home/james/.nave/src/0.4.3/deps/v8/src/checks.cc

Here's what the same checks.cc looks like with the standard node build:

g++ -o obj/release/checks.o -c -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -O3 -fomit-frame-pointer -fdata-sections -ffunction-sections -ansi -fno-rtti -fno-exceptions -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -O3 -fomit-frame-pointer -fdata-sections -ffunction-sections -ansi -DV8_TARGET_ARCH_X64 -DENABLE_VMSTATE_TRACKING -DENABLE_LOGGING_AND_PROFILING -DENABLE_DEBUGGER_SUPPORT -I/usr/local/src/node/deps/v8/src /usr/local/src/node/deps/v8/src/checks.cc

With nave the build would fail with something like:

$ nave use 0.4.3

...

g++ -o obj/debug/checks.o -c -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -g -O0 -ansi -fno-rtti -fno-exceptions -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -pedantic -m64 -g -O0 -ansi -DV8_TARGET_ARCH_X64 -DENABLE_DISASSEMBLER -DDEBUG -DENABLE_VMSTATE_TRACKING -DENABLE_LOGGING_AND_PROFILING -DENABLE_DEBUGGER_SUPPORT -DV8_ENABLE_CHECKS -DOBJECT_PRINT -I/home/james/.nave/src/0.4.3/deps/v8/src /home/james/.nave/src/0.4.3/deps/v8/src/checks.cc

make: *** [program] Killed

Failed to make 0.4.3

fail

james@ubuntu:~$ Killed

Killed

g++: Internal error: Killed (program cc1plus)

Please submit a full bug report.

See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.

Am I using nave incorrectly?  Are there ways to coax nave to use the same switches as node's default build?

thank you,

-- James

[Ryan Dahl]

It seems that nave is building both the debug and release build?

[Ryan Dahl]

Do you get errors when you build from the tarball?

[James Cooper]

Hi Ryan,

Great question.  Yes, I just downloaded the 0.4.3 tarball and it built fine on the same VM with the standard: ./configure; make  sequence

Your other message suggested that nave is using debugging options during its build.  I wonder if there's a way to turn that off?

It sounds like this may be a nave-specific issue.  Please let me know if I should just open a ticket on the nave github project.

thanks for your help

-- James

[Ryan Dahl]

Nave issue, yes.

[James Cooper]

Sounds good.  I logged this:

https://github.com/isaacs/nave/issues/10

thanks again

-- James