Why doesn't Spidermonkey in MacPorts depend on autoconf213?

[adamv]

The Spidermonkey port in MacPorts doesn't call autoconf and doesn't pull in a weird old version of autoconf:

https://trac.macports.org/browser/trunk/dports/lang/spidermonkey185/Portfile

We should "do what they do" and drop the weird autoconf dep.

[cooljeanius]

That's probably be a better question to ask the MacPorts project themselves: https://trac.macports.org/ticket/39358

[adamv]

Spidermonkey compiled for me on Lion without any autoconf stuff.

Will try on Snow Leopard later.

I don't have a Leopard machine to test on.

[mistydemeo]

Spidermonkey has had its private autoconf since fbf398f, when we were packaging a very different version, and it looks like it was never revisited. My guess is it hasn't been necessary at least since we went to 1.8.5 in 2011.

[mistydemeo]

It also builds for me on 10.6 without any autoconf steps. I can test on Tiger and Leopard, but I'm basically 100% sure it's totally unnecessary.

[adamv]

@cooljeanius you can close that issue you opened.

[cooljeanius]

@cooljeanius you can close that issue you opened.

That's ok, @larryv already closed it as "wontfix" for me