On Wed, 04 Jul 2012 01:23:04 +0200, Ole wrote:
> The JS_FS_ etc. macros were already in my patch. I guess they didn't
> made it into the repository
> because there wasn't an additional #ifdef JS_VERSION <= 170
>
> So, it's maybe worth a second try.
I'll let you handle that :)
> So, finally I want to suggest that you also try to compile 1.7, it
> would be better if we both
> use the same "old" version. 1.7 should be easy to port. At least as
> easy as 1.5. Then
> we don't have to figure out difference between 1.5 and 1.7...
I'll give it a try when I get time - might not be for a couple of
weeks though. Unfortunately it wasn't me who ported 1.5 so I'm not
exactly wure what was changed to get it to work.
> Is there anyone with big-endian and working spidermonkey 1.8 jsconsole?
> I do not have problems when running
> scripts directly, just when starting up the interactive jsconsole. It
> happens during JS_NewObjectWithPrototype.
I get a crash with my Spidermonkey 1.8.5 library, but I didn't build
the console so I haven't tried that. A newer version is included with
Timberwolf (I'm trying to get hold of the includes, but it has a lot
of dependencies so I'm not sure whether it is a good idea anyway),
that doesn't have the standalone console either, but the library
works.
I think my 1.8.5 problem is because it's trying to use JIT even though
I (tried to) disable it.
Chris
No comments:
Post a Comment