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

Many missing files in header archive for v17.0.0 #704

Closed
kriszyp opened this issue Oct 19, 2021 · 4 comments
Closed

Many missing files in header archive for v17.0.0 #704

kriszyp opened this issue Oct 19, 2021 · 4 comments

Comments

@kriszyp
Copy link

kriszyp commented Oct 19, 2021

When trying to compile native packages, compiling the v8 include headers fails due to missing header files, including v8-weak-callback-info.h, v8-function-callback.h, v8-callbacks.h, and others. The headers download at https://nodejs.org/dist/v17.0.0/node-v17.0.0-headers.tar.gz does not include all the headers referenced by the included v8 headers. Here is an example compilation error:

c:\users\...\appdata\local\node-gyp\cache\17.0.0\include\node\v8-function.h(11): fatal error C1083: Cannot open inclu
de file: 'v8-function-callback.h': No such file or directory (compiling source file ..\src\node-lmdb.cpp) [C:\dev\lmdb-
store\build\lmdb-store.vcxproj]

I assume V8 9.5 had some refactoring, splitting up some header files, and the new headers just need to be included header archive.

@richardlau
Copy link
Member

Refs nodejs/node#40423. cc @targos

@targos
Copy link
Member

targos commented Oct 19, 2021

TBH I assumed CITGM would catch any mistake here.

@targos
Copy link
Member

targos commented Oct 19, 2021

Hopefully it's fixed in nodejs/node#40526

targos added a commit to targos/node that referenced this issue Oct 19, 2021
targos added a commit to nodejs/node that referenced this issue Oct 20, 2021
Fixes: nodejs/Release#704

PR-URL: #40526
Fixes: #40529
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
@kriszyp
Copy link
Author

kriszyp commented Oct 20, 2021

Thank you so much for the quick response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants