Build fails on Ubuntu 14.04 with "make: -D_LARGEFILE_SOURCE: Command not found"

[severin-lemaignan]

Trying to compile atom on a Ubuntu 14.04 64bits box, its fails with:

make: -D_LARGEFILE_SOURCE: Command not found
make: *** [Release/obj.target/minidump_stackwalk/deps/breakpad/src/third_party/libdisasm/ia32_implicit.o] Error 127

Using g++ (Ubuntu 4.8.2-19ubuntu1) 4.8.2 and GNU Make 3.81.

Any idea?

[severin-lemaignan]

Failed both with Ubuntu's stock npm and Chris Lea PPA (node -v v0.10.28 and node-gyp -v v0.13.0).

[rhoconlinux]

I confirm the issue also in Ubuntu 14.04 64bit:
http://pastebin.com/raw.php?i=4Q7na1At

[g0xA52A2A]

@severin-lemaignan this may sound silly but is make in your $PATH? Can you post the full output?

@rhoconlinux are you seeing the same make issue? Your pastebin link refers to a gyp issue.

[severin-lemaignan]

@George-B Yes, make is in my path :-)
Full output (script/build 2>&1 | curl -F 'clbin=<-' https://clbin.com) here: https://clbin.com/HKVn6

Since I'm completely new to gyp, I do not know how to perform a VERBOSE compilation that could hint where the error actually lays...

[PierreGambarotto]

After installing build-essential on 14.04 64 bits, my build goes a little further, but finally fails at the end with :

Installing modules ✓
Deduping modules ✓

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:998:11)
    at Process.ChildProcess._handle.onexit (child_process.js:789:34)

[g0xA52A2A]

@severin-lemaignan Likewise I'm not very familiar with gyp or node. You may have some luck following this #2029 (comment) regarding gyp provided via npm rather than apt.

[severin-lemaignan]

@George-B Indeed, following steps in #2029 fixed the issues... seems that node is still at the black magic level for me...

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!