-
Notifications
You must be signed in to change notification settings - Fork 93
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
Update to V8 12.9 #342
Update to V8 12.9 #342
Conversation
Removes context.idle_notification because the V8 API it uses has been removed with no real replacement. V8 suggests to use Isolate::MemoryPressureNotification() instead but that's not really the same thing and overlaps significantly with context.low_memory_notification. Remove the stale object marshalling section from the README.
@@ -19,7 +19,7 @@ | |||
$CXXFLAGS += " -g" unless $CXXFLAGS.split.include? "-g" | |||
$CXXFLAGS += " -rdynamic" unless $CXXFLAGS.split.include? "-rdynamic" | |||
$CXXFLAGS += " -fPIC" unless $CXXFLAGS.split.include? "-rdynamic" or IS_DARWIN | |||
$CXXFLAGS += " -std=c++17" | |||
$CXXFLAGS += " -std=c++20" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to update the README for compiler requirements too? https://github.com/rubyjs/mini_racer?tab=readme-ov-file#installation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, those are way out of date. Updated with the compiler recommendations from node's BUILDING.md
any ideas why all the tests are failing? I think it is struggling with bundle for some reason. |
You can do libv8-node releases now, right? If you make one, I'll restart CI and things should - fingers crossed - be green. |
Will do tomorrow
…On Wed, 5 Feb 2025 at 5:48 pm, Ben Noordhuis ***@***.***> wrote:
@SamSaffron <https://github.com/SamSaffron>
Could not find gem 'libv8-node (~> 23.6.1.0)', which is required by gem
You can do libv8-node releases now, right? If you make one, I'll restart
CI and things should - fingers crossed - be green.
—
Reply to this email directly, view it on GitHub
<#342 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAABIXLBXVQEQ2VXDJZW7332OGX3HAVCNFSM6AAAAABWPMGIV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVHAZTEMJZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Removes context.idle_notification because the V8 API it uses has been removed with no real replacement.
V8 suggests to use Isolate::MemoryPressureNotification() instead but that's not really the same thing and overlaps significantly with context.low_memory_notification.
Remove the stale object marshalling section from the README.
Needs a libv8-node release from its node-23 branch first