-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-gyp build error #1187
Comments
The contextify readme says this: "YOU DON'T NEED THIS MODULE ON NODE >= 0.12" As to the build error itself, |
No Luck. Still the same issue even after removing the |
Are you still having this issue? If yes, can you post the current output you get when building? |
Hi, i think this is related, if not just ignore. make: *** [Release/obj.target/erbium/src/erbium.o] Error 1 npm ERR! [email protected] install: npm ERR! Please include the following file with any support request: |
@ricardoSa84 looks like an issue with FYI if you raise issues in two different repos about the same problem it's good practice to link between them. 1248/node-erbium#1 |
@gibfahn Sorry, noobie error. Thought it was because of this module. Saw that that one was really old but as the error had this related in building and saw this build error thought it might be the same. Tanks |
@abishekrsrikaanth Have you had any progress with this issue? Do you have any new information to share? |
I get the similar error, could someone can help me?thank you
|
@liuwensa this could be a problem with |
npm ERR! [email protected] install: |
@sakshi094 This is a bug in |
@refack --no-optional did not helped |
downgrading version of node helped brew unlink node brew link [email protected] |
@sakshi094 Not a good idea. Node.js v0.12 is unmaintained and has known security vulnerabilities. |
ohh .. thn .. what is supposed to be done @bnoordhuis ? do u have any good idea .. ? |
Depends on what issue you ran into. npm bug? Try downgrading to the latest npm@4. If a module fails to build, it's possible it hasn't been updated for newer versions of node.js (ex. threads_a_gogo, mentioned above.) You are probably better off not using it (because it's unlikely to be maintained) than downgrading node. |
Okay .. @bnoordhuis thanks for the info .. will try it this way .. let me see if i get anything new and revert back with new queries. |
Same issue here:
Anybody? |
I get the following error every time I run my build, could someone advice what might be wrong and how to fix it?
My node versions
The text was updated successfully, but these errors were encountered: