Skip to content
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

Error while compiling node-gyp (indirect dependency for labirinto) #198

Closed
proycon opened this issue May 17, 2021 · 4 comments
Closed

Error while compiling node-gyp (indirect dependency for labirinto) #198

proycon opened this issue May 17, 2021 · 4 comments

Comments

@proycon
Copy link
Owner

proycon commented May 17, 2021

I received reports that node-gyp, a dependency for node-sass with is in turn a dependency for labirinto, fails to compile on some systems:

npm ERR! /home/aparikh/.node-gyp/16.1.0/include/node/v8-internal.h:452:38: error: ‘remove_cv_t’ is not a member of ‘std’
npm ERR! /home/aparikh/.node-gyp/16.1.0/include/node/v8-internal.h:452:38: note: suggested alternative: ‘remove_cv’
npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
npm ERR!                                       ^~~~~~~~~~~
npm ERR!                                       remove_cv
npm ERR! /home/aparikh/.node-gyp/16.1.0/include/node/v8-internal.h:452:50: error: template argument 2 is invalid
npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
npm ERR!                                                   ^
npm ERR! /home/aparikh/.node-gyp/16.1.0/include/node/v8-internal.h:452:63: error: ‘::Perform’ has not been declared
npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
npm ERR!                                                                ^~~~~~~
npm ERR! /home/aparikh/.node-gyp/16.1.0/include/node/v8-internal.h:452:63: note: suggested alternative: ‘herror’
npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
npm ERR!                                                                ^~~~~~~
npm ERR!                                                                herror
npm ERR! make: *** [Release/obj.target/binding/src/binding.o] Error 1
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/vol/tensusers3/aparikh/laparikh/src/labirinto/node_modules/node-gyp/lib/build.js:262:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:365:28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Linux 5.4.0-60-generic
npm ERR! gyp ERR! command "/vol/tensusers3/aparikh/laparikh/src/nvm/versions/node/v16.1.0/bin/node" "/vol/tensusers3/aparikh/laparikh/src/labirinto/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /vol/tensusers3/aparikh/laparikh/src/labirinto/node_modules/node-sass
npm ERR! gyp ERR! node -v v16.1.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

I'm not sure what the exact cause is at this point. But often users do who install LaMachine locally are not interested in labirinto (the portal page) as they use the command line anyway, the problem can be circumvented by setting the configuration option ignore_npm_errors: "yes", either do so at installation time in your editor, or in an existing installation as follows:

lamachine-config ignore_npm_errors yes

Then simply run lamachine-update again.

@proycon proycon self-assigned this May 17, 2021
@proycon
Copy link
Owner Author

proycon commented May 17, 2021

Alternative, simply remove labirinto from the installation manifest at install time or using lamachine-update --edit in existing installations.

@Aditya3107
Copy link

I removed the line of labirinto from the installation manifest by lamachine-update --edit and did the lamachine-update. The installation worked out successfully for me.
Thanks a ton.

@proycon
Copy link
Owner Author

proycon commented Jun 2, 2021

The auto-correction option I tried to implement to fix this doesn't seem to help, I ran across this issue again now.

@proycon
Copy link
Owner Author

proycon commented Jul 14, 2021

The new labirinto v0.2.6 should no longer have this problem

@proycon proycon closed this as completed Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants