This is not a 32/64 bit issue, as I'm seeing this on my 64 bit Ubuntu 17.10 system. The full, unedited log built with SAL_LOG="+WARN.+INFO.xmlsecurity+INFO.comphelper.crypto" Can be found here: https://pastebin.com/inwx0Hu0 The previous log was heavily trimmed to reduce size. While the OS is different both builds share the same external drive. Could the path length be a problem? (I trimmed the full path in the previous log) Or could this be like the "Unit test PythonTest_solenv_python failing on est_gbuildtojson" issue where a make clean isn't enough and I have to manually remove some file from the source tree? -Luke