Stylo builds won't work on our current OS X 10.7 builders (bug 1365993). While cross-compilation is a better long-term solution, we're going to experiment with upgrading an existing builder to a newer version of OS X + XCode to try to get stylo unblocked. We'll need someone to get existing build variants running on the experimental 10.10 builder being setup in bug 1368127, documenting the config, tools, and install steps required to make it work. If parallel experiments in fixing the performance issues with cross-compiled builds don't pan out (bug 1338651), this work will give us a starting point for a potential rolling upgrade of the Mac builders.

I have a login on the 10.10 test machine and will evaluate build results. I don't know how our automation build harness gets invoked though, so help on that would be appreciated.

We're working through this on IRC.

Thanks to excellent help form catlee, aki, and jlund, I was able to manually launch a mozharness build, similar to what buildbot would have done. It successfully checked out and built mozilla-central, and I was able to run the resulting build. I didn't test artifact upload or other integration pieces, or run any tests. We also need to verify beta, release, and esr52 build. But it seems the basics are there. I was also able to do a developer build using toolchains downloaded from tooltool. A developer build with --enable-stylo hit bug 1368163, which isn't surprising since I've seen it on my local laptop with macOS 10.12.15, so that's still a blocker for stylo. I'll try beta/release/esr52 next week.

Ralph, does your Cocoa framework fix for cargo crash bug 1365993 mean that we no longer need to investigate updating the OS X 10.7 builders to a newer OS X version (for Stylo, at least)?

(In reply to Chris Peterson [:cpeterson] from comment #4) > Ralph, does your Cocoa framework fix for cargo crash bug 1365993 mean that > we no longer need to investigate updating the OS X 10.7 builders to a newer > OS X version (for Stylo, at least)? The work-around in bug 1365993 means stylo is not currently blocked by the builders being 10.7. We should still update because there will continue to be issues.

Beta 54 and Release 53.0.4 built and worked on the 10.10 loaner. The esr52 branch failed because it's still using build/macosx/universal/mozconfig.common which specifies ac_add_options --with-macos-sdk=/Developer/SDKs/MacOSX10.7.sdk. That mozconfig wasn't removed until bug 1339182 (Firefox 54) but releng must have switched the chosen config earlier than that since release builds. We can work around this by backporting either change to a non-universal build or using a tooltool-packaged sdk.

For reference, here's the script I was using to invoke mozharness. Running `/bin/sh launch.sh beta` should boostrap and run a build of the latest beta revision in the current directory.

(In reply to Ralph Giles (:rillian) | needinfo me from comment #6) > We can work around this by backporting either change to a non-universal > build or using a tooltool-packaged sdk. We can't backport the change because we agreed to support Silverlight in esr52, which is a 32-bit plugin. So we'd need to go the tooltool route here. Thanks to Philor for pointing out the issue, bug 1295375.

catlee, now that Mac cross builds are in production, can we WONTFIX this bug (and its dependencies) about upgrading the OS X builders from OS X 10.7 to 10.10?

We just enabled nightly updates for the cross-compiled builds, so yeah, not going to pursue the 10.10 builders now.