On Friday, November 1, 2019 at 9:59:30 AM UTC-5, Tom Ritter wrote: > On Thursday, October 31, 2019 at 10:22:00 PM UTC, kul...@gmail.com wrote: > > On Thursday, October 31, 2019 at 10:06:42 AM UTC-5, Tom Ritter wrote: > > > On Thursday, October 31, 2019 at 1:53:46 PM UTC, kul...@gmail.com wrote: > > > > On Wednesday, October 30, 2019 at 3:00:37 PM UTC-5, Tom Ritter wrote: > > > > > On Saturday, October 26, 2019 at 2:07:41 PM UTC, kul...@gmail.com > > > > > wrote: > > > > > > I'm not entirely sure where to extract the nsis tarball to - it > > > > > > looks like the instructions about the "annoying situation" refer to > > > > > > building it? At any rate, I extracted it to the root of the > > > > > > repository, with no luck. > > > > > > > > > > Try extracting nsis to /builds/worker/fetches/mingw32 - so it would > > > > > run from /builds/worker/fetches/mingw32/bin > > > > > > > > Unfortunately that didn't help - it still failed with the same error. I > > > > actually have no use for the installer - a simple zip(-like) output is > > > > fine with me. Is there a switch for mach that doesn't build the NSIS > > > > installer? > > > > > > I don't know if we have a switch, but I'm pretty sure we used to do > > > this... > > > > > > Try replacing > > > https://searchfox.org/mozilla-central/rev/1fe0cf575841dbf3b7e159e88ba03260cd1354c0/moz.configure#542-559 > > > with just 'return'. I *think* this should cause MAKENSISU to be blank, > > > and us to skip over the installer.... > > > > Yup, that worked! But of course, another issue: The executables created by > > the compiler don't look like they have the proper Windows EXE header - > > running firefox.exe from {obj_dir}/dist/bin/browser on a Windows machine > > says there's a side-by-side error, and running crashreporter.exe yields > > this message: "nss3.dll is either not designed to run on Windows or it > > contains an error." > > > > I'm running Ubuntu 18.04 x64. The .mozconfig file I'm using is lifted > > directly off the wiki page, and modified it to include the paths of the > > various tools. > > > > Any ideas on what I could poke at to resolve this (hopefully) final issue? > > Thanks! > > Hrm. I'm not sure. When you moved the files you're sure you copied the files > and not symlinks, right? > > You can try running ./mach build --verbose and comparing select lines from > your output to the log from a Taskcluster build output (like > https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=274073642 for > x64 debug). (Click the raw log icon that's above the green 'success' line in > the bottom pane, next to the icon that actually says 'log') I would diff > individual lines like the one containing "-o firefox.exe" and "-o xul.dll" > and see if you have parameters or executables different....
I zipped up the entire bin directory, so hopefully that was the right thing to do. Thanks for the diffing idea! I'll dig into that over the weekend. _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
