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

Build with clang instead of gcc #61

Merged
merged 2 commits into from
Sep 13, 2024
Merged

Conversation

bnoordhuis
Copy link
Collaborator

We may be hitting a compiler bug that is causing segfaults in production so see if switching compilers makes the problem go away.

We may be hitting a compiler bug that is causing segfaults in production
so see if switching compilers makes the problem go away.
@bnoordhuis
Copy link
Collaborator Author

Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Not a seamless upgrade then 🤦

@SamSaffron SamSaffron merged commit 4060e5c into rubyjs:node-22 Sep 13, 2024
23 of 24 checks passed
@lloeki
Copy link
Collaborator

lloeki commented Sep 14, 2024 via email

@SamSaffron
Copy link
Collaborator

yeah @lloeki coaxing this to use clang is not super easy... I thing platform also insists on using GCC here:

libv8-node/libexec/platform

Lines 100 to 107 in 7249c5d

x86_64-*linux*)
CC='x86_64-linux-gnu-gcc'
CXX='x86_64-linux-gnu-g++'
CC_host='gcc'
CXX_host='g++'
STRIP='x86_64-linux-gnu-strip'
configure_flags='--dest-cpu=x86_64 --cross-compiling --dest-os=linux'
;;

We may need to edit this as well ... I changed the container now ... but looking at build log from previous commit ... no clang yet

May change these lines next

@SamSaffron
Copy link
Collaborator

image

@bnoordhuis bnoordhuis deleted the clang branch September 14, 2024 18:38
@bnoordhuis
Copy link
Collaborator Author

bnoordhuis commented Sep 14, 2024

We may need to edit this as well ... I changed the container now ... but looking at build log from previous commit ... no clang yet

It's curious how it uses clang++ for some things and ccache x86_64-linux-gnu-g++ for others. I'll look into it.

edit: I see you've fixed it already, nice!

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 this pull request may close these issues.

3 participants