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 On Tuesday, April 14, 2015 at 2:22:30 AM UTC+2, Aria Stewart wrote: > > 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 > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/13826b9a-f052-4318-9486-83fc06a268d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
