What's Wrong with GLIBCXX_3.4.26?

If you met the following error, please check this post out for a solution.

java.lang.UnsatisfiedLinkError: /tmp/libjavet-v8-linux-x86_64.v.0.8.4.so: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /tmp/libjavet-v8-linux-x86_64.v.0.8.4.so)

Javet v0.8.4 is Released

 

• Upgraded Node.js to v14.16.1 (2021-04-06)
• Upgraded V8 to v9.0.257 (2021-02-24)

https://github.com/caoccao/Javet/

Javet v0.8.3 is released

• Added V8Runtime.lowMemoryNotification() and V8Runtime.idleNotificationDeadline()
• Added V8Host.setMemoryUsageThresholdRatio(), V8Host.enableGCNotification(), and V8Host.disableGCNotification()
• Updated JavetEnginePool to be lock free
• Added autoSendGCNotification to JavetEngineConfig
• Moved JavetCallbackContext management from V8ValueFunction to V8
• Added JavetPromiseRejectCallback for V8 mode

https://github.com/caoccao/Javet/

Javet v.0.8.1 is released.

https://github.com/caoccao/Javet

• Enabled declarative function interception
• Enabled custom object converter in function callback
• Added allowEval to JavetEngineConfig
• Refactored built-in module API for Node.js mode

What does Embedding Node.js and V8 Development Really Mean?

I've been asked quite a few times on how long I spent embedding Node.js. Well, it took almost 3 weeks to unlock Node.js v14.16.0 for Linux and Windows.

I started from the Windows one and it was quite hard. After settling down the Windows version, I jumped into the Linux one. It was a journey full of desperation that would almost kill this project. Finally, I made it. That's Javet.

That may partially explain why I don't intend to support MacOS / Android by myself. Any volunteers?