There is a new JVW_BUILDS_DIR.TRY.ZIP at this URL: http://www.meer.net/~dougt/mozdrop/JVW_BUILDING/JVW_BUILDS_DIR.TRY.ZIP You also have to change an enum in the file extensions\transformiix\source\xpath\ExprLexer.h file. At around line 60: class Token { public: /** * Token types */ enum Type { //-- Trivial Tokens NULL_TOKEN = 1, LITERAL, NUMBER, CNAME, FUNCTION_NAME, VAR_REFERENCE, .... In other words, change the "ERROR = 0, NULL_TOKEN, ..." to be "NULL_TOKEN = 1, ..." I have included that header file in this email as well. This change should (hopefully) be checked into CVS VERY shortly. Here as well is a new set of instructions that work really well for the ARM_PPC, ARM_PPC_DBG, and ARM_SMART builds, but have something strange going on for the EMU_PPC and EMU_PPC_DBG builds. STEP 1: Set up your C:\BUILDS directory: c: cd \ \cygwin\bin\unzip C:\builds_DIST_BITS\JVW_BUILDS_DIR.TRY.ZIP cd \builds call setenv_arm_ppc.bat find -iname *.exe -exec chmod 777 '{}' ; find -iname *.dll -exec chmod 777 '{}' ; STEP 1A: COPY WGET BINARIES FROM C:\BUILDS\OTHER_CYGWIN_TOOLS\WGET INTO C:\CYGWIN\BIN STEP 2: DO ONLY ONCE ON ANY GIVEN PC! call c:\builds\02_do_once.bat STEP 3: Pull Down the source code by running: call c:\builds\03_PullDownSrcCode.bat STEP 3A: Modify the file extensions\transformiix\source\xpath\ExprLexer.h as described above STEP 4: Build actual executables by running one of the following: FOR PPC DEVICE-SPECIFIC BINARIES: call c:\builds\04_make_arm_ppc.bat FOR PPC DEVICE-SPECIFIC DEBUG BINARIES: call c:\builds\04_make_arm_ppc_dbg.bat FOR PPC EMULATOR-SPECIFIC BINARIES: call c:\builds\04_make_emu_ppc.bat FOR PPC EMULATOR-SPECIFIC DEBUG BINARIES: call c:\builds\04_make_emu_ppc_dbg.bat FOR SMARTPHONE DEVICE-SPECIFIC BINARIES: call c:\builds\04_make_arm_smart.bat