Repository navigation
core.h not found #20921
Description
Activity
My guess is that header isn't included in the headers tarball that node-gyp downloads.
More info: The Node core
core.hreference was added as part of this commit 9349e15.My guess is that header isn't included in the headers tarball that node-gyp downloads.
They (#20789 added others) aren't:
Lines 161 to 192 in 5cbb905
def headers(action): action([ 'common.gypi', 'config.gypi', 'src/node.h', 'src/node_api.h', 'src/node_api_types.h', 'src/node_buffer.h', 'src/node_object_wrap.h', 'src/node_version.h', ], 'include/node/') # Add the expfile that is created on AIX if sys.platform.startswith('aix'): action(['out/Release/node.exp'], 'include/node/') subdir_files('deps/v8/include', 'include/node/', action) if 'false' == variables.get('node_shared_libuv'): subdir_files('deps/uv/include', 'include/node/', action) if 'true' == variables.get('node_use_openssl') and \ 'false' == variables.get('node_shared_openssl'): subdir_files('deps/openssl/openssl/include/openssl', 'include/node/openssl/', action) subdir_files('deps/openssl/config/archs', 'include/node/openssl/archs', action) subdir_files('deps/openssl/config', 'include/node/openssl', action) if 'false' == variables.get('node_shared_zlib'): action([ 'deps/zlib/zconf.h', 'deps/zlib/zlib.h', ], 'include/node/') I'm not sure if the correct fix is to add them to the install script, or take them out of
node.hand move them tonode_internals.h.Reacted by John-David DaltonI'm not sure if the correct fix is to add them to the install script, or take them out of node.h and move them to node_internals.h.
Probably the latter.
Reacted by Refael Ackermannpretty big bug! pls fix asap
Likely best to move the core.h reference to node_internals.h.
Actually, I take that back... fixing the install.py is likely the better choice. Investigating now.
Reacted by Derek SiffordFix in #20925 ... once that lands a new 10.2.1 release needs to be spun up.
My
npm rebuild node-sassfails in production today and cannot go live with the next version promised for today :(Reacted by Lukasz SzkupJust updated to node 10.2 and have same issue with missing core.h header.
I have now updated
node-sassin my project and everything started working again. Or maybe in the meantime, someone changed the version of Node on Heroku.I just copied manually from git rep core.h into ~/node-gyp/10.2.0/include/node/, and then I also had to copy callback_scope.h and exceptions.h.
However after I did that, I got again error with include macro NODE_MODULE_X
(node::addon_register_func) (regfunc),
and my c++ module still fails to compile.
Reacted by Doru MoisaHmm, I was able to compile with clang, but compilation with gcc fails. Everything else on my system compiles just fine with gcc :-(
Note: fix has been identified and is in review. We will be verifying the fix and if it doesn't work we can revert the commit that's at fault and revisit that change. Either one should land today and an updated release will be coming out quickly.
Reacted by Artur, John-David Dalton, Al McKinlay, cybai (Haku), Jon Gjengset, Brian Cooke, Niklas Mischkulnig, Julian Simioni, Amish Shah, rehtlaw and 2 more3 remaining items
hey good work guys but how could NodeJS be released without running basic tests to build popular native modules? how? explain!
Reacted by Lukasz SzkupOur regular ci runs do not currently include adequate coverage of native modules built using the tarball. We've got an issue open to fix that and we always welcome pull requests that help.
Reacted by cybai (Haku)Reacted by Rick MakReacted by idibidiartReacted by Weiliang LiOur CI also got brought down by this bug....Plz fix it asap 🙏
Already fixed. Already released.
Hmm not showing up here and my CI keeps grabbing 10.2.0
- Docker images usually lag just a bit. On May 24, 2018 21:27, "Jerod King" <notifications@github.com> wrote: Hmm not showing up here and my CI keeps grabbing 10.2.0 https://hub.docker.com/_/node/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20921 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAa2eahESpB8NkY-fjI_zKsEdczSI56hks5t14gWgaJpZM4ULamU> .
PR for official image is still open: docker-library/official-images#4394
I noticed that even after a merge there it takes some extra time till image is really available.Here's the workaround I use until the fixed version will be available:
https://gist.github.com/moisadoru/3c894abf13474f48b5c3ce4d84a64e4e
Reacted by Andreas Kohn and Gireesh Punathil- added 2 commits that reference this issue
on May 25, 2018 I've installed node 10.2.1 to fix the core.h issue with zeromq, but i'm running into this problem :
╭─pciavald@thinkpad-manjaro ~/Documents/iota-messenger ‹invite*› ╰─➤ nvm use 10.2.1 nvm is not compatible with the npm config "prefix" option: currently set to "" Run `npm config delete prefix` or `nvm use --delete-prefix v10.2.1` to unset it. ╭─pciavald@thinkpad-manjaro ~/Documents/iota-messenger ‹invite*› ╰─➤ node --version 11 ↵ v10.2.0 ╭─pciavald@thinkpad-manjaro ~/Documents/iota-messenger ‹invite*› ╰─➤ nvm use --delete-prefix v10.2.1 ╭─pciavald@thinkpad-manjaro ~/Documents/iota-messenger ‹invite*› ╰─➤ node --version 11 ↵ v10.2.1 ╭─pciavald@thinkpad-manjaro ~/Documents/iota-messenger ‹invite*› ╰─➤ yarn [1] 24504 segmentation fault (core dumped) yarnsame goes with npm
- added a commit that references this issue
on Jun 26, 2018 in my case: node 10.2 install error, but ok with node 11.6
- added a commit that references this issue
on Jan 14, 2019 - added a commit that references this issue
on Apr 2, 2019
I noticed using Node 10.2.0 that the
sleeppackage now fails to build with the following error(it didn't fail with 10.1.0):
The problem line appears to be
node/src/node.h
Line 53 in 82f1811