Node is intended to be used with the version of v8 that comes in the deps folder.
It is my understanding that V8's policy is to maintain ABI consistency within a release family. That's why we don't change v8 release branches, and only update the smallest version within a node stable branch. If you choose to link against a different version of v8 (because, of course, you have SO MANY programs using v8, it would be a TRAGEDY if each of them had their own copy, because disk space is SO EXPENSIVE), then it's your responsibility to pick a version that works, or deal with the consequences. If the bundled copy of V8 doesn't compile or run properly with node, then I care about that, very very much. That's a release-blocker; if it's in a release, it's an emergency. If the newest version of v8 doesn't build with node master, then that's interesting, and probably something we need to fix soonish. If some other version of v8 doesn't build against a stable branch? I don't care even a little. Not to sound too harsh, but we make the "easy way" easy for a reason. On Thu, May 10, 2012 at 1:25 AM, Oleg Efimov (Sannis) <[email protected]> wrote: > Related issue in node tracker: > https://github.com/joyent/node/issues/3184 with stack. > Node works fine with v8 3.8.x but not with 3.10.x > > четверг, 10 мая 2012 г., 4:35:03 UTC+4 пользователь mscdex написал: >> >> I am curious about getting a more recent version of v8 running in >> either node 0.7.x or 0.6.x. >> >> I tried swapping out v8 in 0.7.8 and 0.6.17 with a copy of v8 3.10.8.4 >> (checking and applying any of node's floating patches on v8) and >> everything seems to compile fine and at least work somewhat, but it >> always segfaults at the end (of the first tick?). >> >> Maybe I'm missing other floating patches or changes? Specifically I >> checked changes/patches made to v8/SConstruct, v8/tools/gyp/v8.gyp, >> and v8/build/common.gypi.
