Created attachment 338062 [details] Build log Looks like the API changed in a non-compatible way. It also broke older versions of chromium; I'm just going to adjust the dependencies there.
From the ChangeLog: 2013-01-15: Version 3.16.5 Removed deprecated functions from V8's external API.
This is known upstream (nodejs). They decided to go with 3.15.xx, and we should explicitly link against it. Let me know if you insist on me finding that commit/discussion.
And for what it's worth, the same issue is discussed here for node 0.8: https://bugs.gentoo.org/show_bug.cgi?id=453654
The nodejs-0.9.9 requires v8:0/3.15.11. It works here ;-)
net-libs/nodejs-0.9.9 doesn't compile with dev-lang/v8-3.14.5.3 on x86, indeed.
It is almost a certainty the dev-lang/v8-3.15* will be removed from the tree in the next 6 months or so due to some security bug. This bug is basically an advance notice that somebody is going to have to deal the nodejs/v8 situation before that point.
Upgrading v8 from 3.14.5.3 to 3.15.11.15 makes nodejs 0.9.9 builds again. So wouldn't it be sufficient to add >=dev-lang/v8-3.15.11.15 to the net-libs/nodejs-0.9.9 ebuild?
*** Bug 457862 has been marked as a duplicate of this bug. ***
I adjusted the dependency to =dev-lang/v8-3.15*. I think this bug should stay open until we have a better solution. + 16 Feb 2013; Mike Gilbert <floppym@gentoo.org> nodejs-0.9.3-r1.ebuild, + nodejs-0.9.9.ebuild: + nodejs-0.9 needs v8-3.15, bugs 457862 and 455788. +
We nowadays use the bundled v8, mainly because they went back to 3.14.x for 0.9.x (becoming 0.10 next week). Lets go with this for a while and see how upstream handles future upgrades. See https://github.com/joyent/node/issues/4489 for a possible discussion on this.
0.9.x is now 0.10.x and we chose to use a in-tree v8. Closing.
