On 07/05/2013 11:46 PM, Bruce Dubbs wrote: > As I go through the packages in the book, I've looked upstream at > spidermonkey. There appear to be two versions: > > js185-1.0.0.tar.gz 31-Mar-2011 > mozjs17.0.0.tar.gz 25-Mar-2013 > > We are using the older version. I do not see any references to this > elsewhere in the book. >
Polkit uses it in current BLFS. It is required for GNOME JS engine (gjs), too. I think newer version of GJS can use SpiderMonkey 17.0, but I am not sure about Polkit. $ grep -r linkend=\"SpiderMonkey\" gnome/platform/gjs.xml: <xref linkend="SpiderMonkey"/> postlfs/security/polkit.xml: <xref linkend="SpiderMonkey"/> > What I find about the newer version is: > > "SpiderMonkey 17 is the JavaScript engine that shipped in Firefox 17." > > "SpiderMonkey 17 is not binary-compatible with previous releases, nor is > it source-code compatible. Many JSAPI types, functions, and callback > signatures have changed, though most of them still have the same names > and do the same things. Applications will need significant changes, but > most of those changes will be detected by the C/C++ compiler, so they > are easy to detect and updating the code is a fairly straightforward job." > > My question is whether we need the later version or the earlier version? > Both? Neither? > > Ken, you added spidermonkey in Jan 2012. Can you give some background? > > -- Bruce > > P.S. There is a new program, js17. > > $ ./js17 --help > Usage: ./js17 [options] [[script] scriptArgs*] > > The SpiderMonkey shell provides a command line interface to the > JavaScript engine. Code and file options provided via the command > line are run left to right. If provided, the optional script argument > is run after all options have been processed. Just-In-Time > compilation modes may be enabled via command line options. > > Version: JavaScript-C 17.0.4esrpre > > Arguments: > script A script to execute (after all options) > scriptArgs String arguments to bind as |arguments| in the shell's global > > Options: > -f --file=PATH File path to run > -e --execute=CODE Inline code to run > -i --shell Enter prompt after running code > -m --methodjit Enable the JaegerMonkey method JIT > -n --typeinfer Enable type inference > -c --compileonly Only compile, don't run (syntax checking mode) > -d --debugjit Enable runtime debug mode for method JIT code > -a --always-mjit Do not try to run in the interpreter before method > jitting. > -D --dump-bytecode Dump bytecode with exec count for all scripts > -b --print-timing Print sub-ms runtime for each file that's run > -U --utf8 C strings passed to the JSAPI are UTF-8 encoded > -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
