Source build error on Voyage Linux (Debian)

50 views
Skip to first unread message

Guy Dillen

unread,
Apr 13, 2015, 8:20:07 PM4/13/15
to nod...@googlegroups.com
Hi,

trying to get nodejs on my Voyage Linux (Debian) based 32-bit machine.

I already:
- Tried the linux 32 binaries: doesn't work.
- Tried package manager: doesn't work
- So that leaves me by building from source (I downloaded the latest source version 0.12.2):

here I get:

Apparently the build process gets stuck on "hydrogen-instructions.cc"

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
make[1]: *** [/opt/node-v0.12.2/out/Release/obj.target/v8_base/deps/v8/src/hydrogen-instructions.o] Error 4
make[1]: Leaving directory `/opt/node-v0.12.2/out'
make: *** [node] Error 2

An idea what's going wrong here?

Thanks.

Aria Stewart

unread,
Apr 13, 2015, 8:22:30 PM4/13/15
to nod...@googlegroups.com
On Monday, April 13, 2015 at 8:20:07 PM UTC-4, Guy Dillen wrote:
Hi,

trying to get nodejs on my Voyage Linux (Debian) based 32-bit machine.

I already:
- Tried the linux 32 binaries: doesn't work.
- Tried package manager: doesn't work

Goodness -- what failures?
 
- So that leaves me by building from source (I downloaded the latest source version 0.12.2):

here I get:

Apparently the build process gets stuck on "hydrogen-instructions.cc"

g++: internal compiler error: Killed (program cc1plus)

I see two likely possibilities there. First, check that you didn't run out of RAM (check dmesg -- "Killed" is what a process hit by the OOM killer would return)

Second, you may have a gcc bug (Or bad RAM!) -- what version of gcc and on what architecture are you?

Aria

Guy Dillen

unread,
Apr 14, 2015, 10:05:24 AM4/14/15
to nod...@googlegroups.com
Hi Aria,

Many thanks.

Indeed it's a memory problem (I'm running on AMD Geode LX800 with 256MB RAM).

So with that I have build Nodejs in a VM with the same Voyage but with more RAM. So now Nodejs has been build successfully.

My question now is:
What (files/folders) do I have to copy from my build-environment to my production environment (the machine with the 256MB) to run Nodejs?

Thanks.
Guy

Aria Stewart

unread,
Apr 14, 2015, 10:16:17 AM4/14/15
to nod...@googlegroups.com
On Tuesday, April 14, 2015 at 10:05:24 AM UTC-4, Guy Dillen wrote:
Hi Aria,

Many thanks.

Indeed it's a memory problem (I'm running on AMD Geode LX800 with 256MB RAM).

So with that I have build Nodejs in a VM with the same Voyage but with more RAM. So now Nodejs has been build successfully.

My question now is:
What (files/folders) do I have to copy from my build-environment to my production environment (the machine with the 256MB) to run Nodejs?

Install into an empty folder as a destdir; everything in there.

try mkdir /tocopy; python tools/install.py install /tmp/tocopy /usr/local

Aria
Reply all
Reply to author
Forward
0 new messages