-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Compiling on Mac cause an error thrown by g++-12 #58219
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
Comments
|
@targos yes! By skipping it, it works. should we update the doc or should we wait for it to work again? |
The documentation should be updated. Would you like to try and open a PR? |
@targos sure! on it. |
vagostep
added a commit
to vagostep/node
that referenced
this issue
May 8, 2025
Currently, there is an error when executing export: CXX=g++-12 on macOS. Without it, it compiles fine. So, we split the step into two caterogies: steps for unix and steps for macOS Fixes: nodejs#58219
vagostep
added a commit
to vagostep/node
that referenced
this issue
May 15, 2025
Currently, there is an error when executing export: CXX=g++-12 on macOS. Without it, it compiles fine. So, we split the step into two caterogies: steps for unix and steps for macOS Fixes: nodejs#58219 Restoring previous BUILDING.md new doc proposal for g++-12 export command removing non related line change restoring end of file restoring comment proposal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
22.x
Platform
Subsystem
No response
What steps will reproduce the bug?
On a brand new Mac, following the BUILDING.md steps, specifically
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
It should compile successfully by following the BUILDING.md steps.
If I skip the
export CXX=g++-12
command, it compiles successfully.Maybe it is a documentation error, or a dependency step that is not working as expected in the latest Mac versions
What do you see instead?
An error:
Additional information
No response
The text was updated successfully, but these errors were encountered: