#29446: spidermonkey: update to 1.8.5 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: akitada@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: spidermonkey -------------------------------------+-------------------------------------- Changes (by ryandesign@…): * keywords: => haspatch Comment: MongoDB 2.0.5 still does not support SpiderMonkey 1.8.5; see upstream bugs [https://jira.mongodb.org/browse/SERVER-2887 2887] and [https://jira.mongodb.org/browse/SERVER-4870 4870] which have some patches but which have not been accepted. 2887 says they might switch from SpiderMonkey to v8 in the future. Meanwhile, as comment:3 says, SpiderMonkey 1.8.5 is required for edbrowse 3.4.8, and probably other programs. The [https://developer.mozilla.org/en/SpiderMonkey/1.8.5 SpiderMonkey 1.8.5 release notes] say "SpiderMonkey 1.8.5 is not binary-compatible with previous releases, nor is it source-code compatible" and also "SpiderMonkey embedders should also be aware that ... Mozilla has no plans to keep the JSAPI, nor the JSDBGAPI stable for embedders. We have chosen to concentrate on performance and correctness as primary concerns instead." They even have separate version numbers for each version of SpiderMonkey—it's "SpiderMonkey 1.8.5 1.0.0" for example. For these reasons it might be smart for us to have separate SpiderMonkey ports for each version of SpiderMonkey. That way each other port that uses SpiderMonkey can decide if and when to upgrade to newer versions. Here's a patch that creates a new spidermonkey185 port. They now use a configure script, so I began from the assumption that our existing patches and workarounds were no longer needed and cleared them away. I had to add back in a patch to fix the creation of the library symlinks when using DESTDIR, and I patched where the headers are installed so as to include the version number in the path. The idea to name the include directory "mozjs185" came from the config.m4 file of php-spidermonkey 1.0.0 which looks for a directory of that name, as one of the possibilities. Because the new js-config script that gets installed also does not have a version number in its name, and it doesn't work right on Darwin, I decided to just delete it and require people to use pkg-config instead. One remaining outstanding issue is that I cannot get it to build universal (using either the default universal variant or the muniversal portgroup), nor for a non-default build_arch. This is a step backward from the existing spidermonkey port but I don't know how to resolve it right now. -- Ticket URL: <https://trac.macports.org/ticket/29446#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS