-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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.exe fails to link #40749
Comments
Should I try building it in visual studio 2019? Later today I'm going to try building it on Ubuntu. |
@nodejs/platform-windows |
Do I have to be a member to use that? |
Are you referring to |
@nodejs/build |
I don't know if this is the source of your problem or not, but https://github.com/nodejs/node/blob/40ab2888f57d11bda4820f871836118d8fec4d22/BUILDING.md#windows says that building on Windows requires Python 3.9, but your output above indicates you are running Python 3.6. |
No that doesn't change anything |
@Derailedzack - where is |
It might be coming from vcpkg |
I have zlib installed in vcpkg |
thanks. Is that an essential component of that installation? is there a way to (if that works then our build scripts might need modification to either i) use the installed zlib, or override that with the one from node, if we are building in windows with the |
The linker errors are gone.
|
I build on windows and I notice some warnings
|
I found This should always shown in CI environment due to clean build. Line 340 in d102d16
rd test in cmd: > rd some_not_existed_file
The system cannot find the file specified.
> echo %errorlevel%
0
>
> rd some_not_existed_file >NUL 2>&1
> echo %errorlevel%
0
> Maybe append |
Version
16.13.0
Platform
Microsoft Windows NT 10.0.19043.0 x64
Subsystem
The standalone Interpretor
What steps will reproduce the bug?
1.Run vcbuild.bat
2.Wait for it to link node.exe
3.Observe linker error
How often does it reproduce? Is there a required condition?
Every time,No
What is the expected behavior?
It shouldn't generate any linker errors
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: