This port is a 3 way "merge" of:
3) kwm@ work: .http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ports/lang/spidermonkey/
The goals were:
- Take the 'best' (subjective, with discretion) bits of each body of work
- Reduce patch work and stay close to upstream
- Lots of OPTIONS for user-choice (with recommended DEFAULTS)
- Include JS version in PORTNAME to support multiple spidermonkey ports.
Thank you kwm@ flo@ and t_j for your feedback, tips and suggestions.
portlint: looks fine.
unittests: FreeBSD 9.0 AMD64
===> Running jstests.py: PASS
===> Running jit_test.py: PASSED ALL
Note 1: all redports builds include 2 x test suite runs (JSTEST & JIT). See
buildlog output for details.
Note 2: There are intermittent test failures in: js1_8_5/extensions/worker-terminate.js
JS shell workers have been removed from upstream, see:
Generated with FreeBSD Port Tools 0.99_6 (mode: new)
I'll take it.
New port added, with minor changes. Thanks!
On Fri, Mar 22, 2013 at 7:34 AM, Mathias Breuninger <
> devel/spidermonkey185 compiles flawlessly on FreeBSD-9.1-RELEASE (PowerPC
> For some reason, the install script does not copy the js exec in
> /usr/local/bin (
> I had to do so manually.
> This port should conflict with devel/spidermonkey17 which installs a js
> exec in /usr/local/bin as well.
> Thank you for the port anyway!
> Mathias Breuninger
I'm nowhere near being well-versed in makefiles, but a quick look through
the install target of the Makefile tells me that js is indeed not being
I guess it is possible to include the installation of js in a similar way
that it is done for js-config. But I'm not sure if that is the right
Forwarding this as a followup to the actual PR that got accepted, done by
developers that actually knew what they were doing. See
Oh, and I think the install of js should be optional. Then
lang/spidermonkey17 and lang/spidermonkey185 wouldn't conflict if js isn't
installed. Just for the people who may need both and dont need the js shell.