I actually couldn't recall what I did before, so I tried it again. 1) Clone https://github.com/tpoechtrager/apple-libtapi 2) pushd apple-libtapi && INSTALLPREFIX=$HOME/cctools ./build.sh && ./install.sh && popd 3) Clone https://github.com/tpoechtrager/cctools-port (we might need to use a specific revision) 4) pushd cctools-port/cctools && ./autogen.sh && ./configure --prefix=$HOME/cctools --with-libtapi=$HOME/cctools --target=x86_64-apple-darwin --enable-tapi-support --with-libtapi=$HOME/cctools --enable-lto-support && make install 5) ln -sf $HOME/cctools/bin/x86_64-apple-darwin-ld $HOME/cctools/bin/ld64 (this might be unnecessary) 5) Clone https://github.com/phracker/MacOSX-SDKs 6) rustup target add x86_64-apple-darwin 7) build firefox with below .mozconfig .mozconfig ``` ac_add_options --target=x86_64-apple-darwin ac_add_options --with-macos-sdk=$HOME/MacOSX-SDKs/MacOSX10.14.sdk mk_add_options "export PATH=$PATH:$HOME/cctools/bin" ``` Now building seems to start working on my local Linux box (but it still takes a lot of times on toolkit/crashreporter/google-breakpad/src/tools/mac/dump_syms/dump_syms now, I mean the build hasn't finished yet). Anyways, as glandium said in comment 16, cctools on CIs has been updated so it seems to me that all we have to do is to upload the new MacOSX tar ball to an appropriate place and use it, I don't know where the place is though, the way to [generate the tar ball is well documented](https://searchfox.org/mozilla-central/rev/3fd53c47864fedb916f0ed8f002f15456324f729/build/macosx/cross-mozconfig.common#13-18). (In reply to Mike Hommey [:glandium] from comment #16) > If someone with a real SDK 10.14 and/or 10.15 can tell whether the files in https://github.com/phracker/MacOSX-SDKs/ are pristine, that would be useful. A fun fact I noticed is that [the SDK 10.14 in the repo was uploaded by kats](https://github.com/phracker/MacOSX-SDKs/commit/ef880f242ffbc4d6db43a143d6f73a11a1778dad), so it is a resonable one I believe.
Bug 1475652 Comment 19 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I actually couldn't recall what I did before, so I tried it again. 1) Clone https://github.com/tpoechtrager/apple-libtapi 2) pushd apple-libtapi && INSTALLPREFIX=$HOME/cctools ./build.sh && ./install.sh && popd 3) Clone https://github.com/tpoechtrager/cctools-port (we might need to use a specific revision) 4) pushd cctools-port/cctools && ./autogen.sh && ./configure --prefix=$HOME/cctools --with-libtapi=$HOME/cctools --target=x86_64-apple-darwin --enable-tapi-support --with-libtapi=$HOME/cctools --enable-lto-support && make install 5) ~~ln -sf $HOME/cctools/bin/x86_64-apple-darwin-ld $HOME/cctools/bin/ld64 (this might be unnecessary)~~ 5) Clone https://github.com/phracker/MacOSX-SDKs 6) rustup target add x86_64-apple-darwin 7) build firefox with below .mozconfig .mozconfig ``` ac_add_options --target=x86_64-apple-darwin ac_add_options --with-macos-sdk=$HOME/MacOSX-SDKs/MacOSX10.14.sdk mk_add_options "export PATH=$PATH:$HOME/cctools/bin" ``` Now building seems to start working on my local Linux box (but it still takes a lot of times on toolkit/crashreporter/google-breakpad/src/tools/mac/dump_syms/dump_syms now, I mean the build hasn't finished yet). Anyways, as glandium said in comment 16, cctools on CIs has been updated so it seems to me that all we have to do is to upload the new MacOSX tar ball to an appropriate place and use it, I don't know where the place is though, the way to [generate the tar ball is well documented](https://searchfox.org/mozilla-central/rev/3fd53c47864fedb916f0ed8f002f15456324f729/build/macosx/cross-mozconfig.common#13-18). (In reply to Mike Hommey [:glandium] from comment #16) > If someone with a real SDK 10.14 and/or 10.15 can tell whether the files in https://github.com/phracker/MacOSX-SDKs/ are pristine, that would be useful. A fun fact I noticed is that [the SDK 10.14 in the repo was uploaded by kats](https://github.com/phracker/MacOSX-SDKs/commit/ef880f242ffbc4d6db43a143d6f73a11a1778dad), so it is a resonable one I believe.