We previously just downloaded a clang binary from llvm.org. However, I think clang is mature and mainstream enough for us to use the system one. The Gitian descriptors have also been changed accordingly (and work).
MarcoFalke if the Gitian Builds fail for this one, it’s because:
In fact, we should probably just subtree tpoechtrager’s SDK generation scripts.
dongcarl added the label
Build system
on Oct 10, 2019
fanquake added the label
macOS
on Oct 10, 2019
laanwj
commented at 6:16 pm on October 10, 2019:
member
We DO need to fix our docs for generating macOS SDKs… Previously we just tarred up MacOSX10.14.sdk, but we also need to copy over the headers as done here
If you need people to re-generate the MacOSX SDK, please document it well and make sure there’s a way that people without Macs can do it (I don’t have access to a Mac anymore, for one). Might want to combine it with the version upgrade.
Edit: oh, you did base it on #16392 already.
dongcarl force-pushed
on Oct 15, 2019
depends: clang 6.0.1
This also removes some now-unnecessary cctools hacks
Co-Authored-By: Cory Fields <cory-nospam-@coryfields.com>
70b0eacf99
build: set minimum supported macOS to 10.1287f9413576
We manually put the toolchain and binutils into the same path in
native_cctools, this is unintuitive. Since we effectively decouple our
toolchain and binutils in this patchset, the make variables should
reflect this as well.
The $(toolchain_path) prefix is removed in the next commit. They are
separate so I can do this scripted-diff.
-BEGIN VERIFY SCRIPT-
find depends -type f -print0 | xargs -0 sed -i "s/_native_toolchain/_native_binutils/g"
find depends -type f -print0 | xargs -0 sed -i "s/toolchain_path/binutils_path/g"
-END VERIFY SCRIPT-
b9c19e68c1
depends: No more binutils_path prefix for CC in site
If we do end up building a compiler inside depends in the future, we can
just add a separate compiler_path prefix and use it here.
See the previous commit for more details.
0d3f3428c9
contrib: macdeploy: Minor README changes.1250d228e1
contrib: macdeploy: Correctly generate macOS SDK
Previously, we did not include the libc++ headers in our SDK creation,
now we can use tpoechtrager's script to correctly do that. The
gen_sdk_package.sh is taken from
https://github.com/tpoechtrager/osxcross/blob/d3392f4eae78f3fa3f1fd065fa423f2712825102/tools/gen_sdk_package.sh
We also document this change.
a0fefee822
dongcarl force-pushed
on Oct 15, 2019
dongcarl
commented at 11:36 pm on October 15, 2019:
member
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
laanwj added this to the "PRs" column in a project
MarcoFalke
commented at 1:51 pm on November 19, 2019:
member
Is it really required to first bump clang to a more recent version and then in the next commit remove the hardcoded clang? Wouldn’t it be more straightforward to just remove the hardcoded clang?
dongcarl force-pushed
on Dec 17, 2019
dongcarl force-pushed
on Dec 19, 2019
dongcarl force-pushed
on Jan 13, 2020
dongcarl closed this
on Jul 9, 2020
fanquake referenced this in commit
1148f3d630
on Jul 16, 2020
sidhujag referenced this in commit
33369338f9
on Jul 18, 2020
fanquake moved this from the "PRs" to the "Done" column in a project
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2024-12-19 03:12 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me