User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Build ID: 20110928134238 Steps to reproduce: From bug 686305 comment 2, I tried downloading jsshell-win32.zip and jsshell-win64-x86_64.zip, tried extracting each of them into their own subdirectory, and tried running js.exe. Neither one worked, and gave the error "the program can't start because mozutils.dll is missing from [my] computer. Try reinstalling the program to fix this problem.". What am I missing, and where can I find mozutils.dll if in fact I need it?
Needs a packaging fix: http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/packager.mk#92
There are two options, really: either include mozutils.dll, or stop linking jsshell to it. Do we have a reason to specifically want jsshell to use jemalloc?
Note: with the landing of bug 414946, the same issue will hit mac, too. Whichever route we take, we can remove the #ifdef in packager.mk, zip will only complain about missing file, but won't fail (iirc its behaviour)
I suspect Spidermonkey hackers will in fact want a JS shell linked with jemalloc.
Created attachment 577705 [details] [diff] [review] Add mozutils library to jsshell distributable I spoke to David, he's fine with me taking this bug. This patch simply adds the mozutils library to the archive file containing jsshell.
I built a try-server version at https://tbpl.mozilla.org/?tree=Try&rev=2b9b32464d81 and tested Linux, Mac OS X, and Windows jsshells and they all run without asking for mozutils
Try run for 2b9b32464d81 is complete. Detailed breakdown of the results available here: https://tbpl.mozilla.org/?tree=Try&rev=2b9b32464d81 Results (out of 15 total builds): success: 13 failure: 2 Builds available at http://email@example.com