|
|
|
|
package=native_cctools
|
|
|
|
|
$(package)_version=2ef2e931cf641547eb8a68cfebde61003587c9fd
|
|
|
|
|
$(package)_download_path=https://github.com/tpoechtrager/cctools-port/archive
|
depends: major upgrade to darwin toolchain
tl;dr: Update to the newer stable toolchain and SDK for OSX without giving up
any backwards compatibility. We can move to clang 3.5 as a next step which
allows use to use libc++ and the 10.10 sdk, but we'll need to find a build that
works in gitian/travis first.
Switch to a new, better maintained fork of cctools:
https://github.com/tpoechtrager/cctools-port
I've forked this and will be working on it some as well:
https://github.com/theuni/cctools-port
This brings in:
cctools v862
ld64: v241.9
It also fixes 64bit builds, so there's no longer any need to use a 32bit clang.
Since clang is no longer tied to an old/crusty 32bit build, clang has been
upgraded to 3.3. Unfortunately, there's a bug in 3.4 that breaks builds. 3.5
works fine, but there are no binary builds compatible with precise, which is
currently used for gitian and travis. We could always build our own if
necessary.
After updating to stable clang/linker/cctools, it's possible to use a more
recent SDK. The current SDK (10.7) through the most recent 10.10 have all been
built/tested successfully, both with and without 10.6 compatibility. However,
10.10 requires clang 3.5.
SDKs >= 10.9 use libc++ rather than libstdc++. This is verified working as well.
10 years ago
|
|
|
$(package)_file_name=$($(package)_version).tar.gz
|
|
|
|
|
$(package)_sha256_hash=6b73269efdf5c58a070e7357b66ee760501388549d6a12b423723f45888b074b
|
depends: major upgrade to darwin toolchain
tl;dr: Update to the newer stable toolchain and SDK for OSX without giving up
any backwards compatibility. We can move to clang 3.5 as a next step which
allows use to use libc++ and the 10.10 sdk, but we'll need to find a build that
works in gitian/travis first.
Switch to a new, better maintained fork of cctools:
https://github.com/tpoechtrager/cctools-port
I've forked this and will be working on it some as well:
https://github.com/theuni/cctools-port
This brings in:
cctools v862
ld64: v241.9
It also fixes 64bit builds, so there's no longer any need to use a 32bit clang.
Since clang is no longer tied to an old/crusty 32bit build, clang has been
upgraded to 3.3. Unfortunately, there's a bug in 3.4 that breaks builds. 3.5
works fine, but there are no binary builds compatible with precise, which is
currently used for gitian and travis. We could always build our own if
necessary.
After updating to stable clang/linker/cctools, it's possible to use a more
recent SDK. The current SDK (10.7) through the most recent 10.10 have all been
built/tested successfully, both with and without 10.6 compatibility. However,
10.10 requires clang 3.5.
SDKs >= 10.9 use libc++ rather than libstdc++. This is verified working as well.
10 years ago
|
|
|
$(package)_build_subdir=cctools
|
|
|
|
|
$(package)_dependencies=native_libtapi
|
|
|
|
|
$(package)_patches=no_fixup_chains.patch
|
depends: major upgrade to darwin toolchain
tl;dr: Update to the newer stable toolchain and SDK for OSX without giving up
any backwards compatibility. We can move to clang 3.5 as a next step which
allows use to use libc++ and the 10.10 sdk, but we'll need to find a build that
works in gitian/travis first.
Switch to a new, better maintained fork of cctools:
https://github.com/tpoechtrager/cctools-port
I've forked this and will be working on it some as well:
https://github.com/theuni/cctools-port
This brings in:
cctools v862
ld64: v241.9
It also fixes 64bit builds, so there's no longer any need to use a 32bit clang.
Since clang is no longer tied to an old/crusty 32bit build, clang has been
upgraded to 3.3. Unfortunately, there's a bug in 3.4 that breaks builds. 3.5
works fine, but there are no binary builds compatible with precise, which is
currently used for gitian and travis. We could always build our own if
necessary.
After updating to stable clang/linker/cctools, it's possible to use a more
recent SDK. The current SDK (10.7) through the most recent 10.10 have all been
built/tested successfully, both with and without 10.6 compatibility. However,
10.10 requires clang 3.5.
SDKs >= 10.9 use libc++ rather than libstdc++. This is verified working as well.
10 years ago
|
|
|
|
|
|
|
|
define $(package)_set_vars
|
|
|
|
|
$(package)_config_opts=--target=$(host) --enable-lto-support
|
|
|
|
|
$(package)_config_opts+=--with-llvm-config=$(llvm_config_prog)
|
|
|
|
|
$(package)_ldflags+=-Wl,-rpath=\\$$$$$$$$\$$$$$$$$ORIGIN/../lib
|
|
|
|
|
$(package)_cc=$(clang_prog)
|
|
|
|
|
$(package)_cxx=$(clangxx_prog)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
ifneq ($(strip $(FORCE_USE_SYSTEM_CLANG)),)
|
|
|
|
|
define $(package)_preprocess_cmds
|
|
|
|
|
mkdir -p $($(package)_staging_prefix_dir)/lib && \
|
|
|
|
|
cp $(llvm_lib_dir)/libLTO.so $($(package)_staging_prefix_dir)/lib/ && \
|
|
|
|
|
cp -f $(BASEDIR)/config.guess $(BASEDIR)/config.sub cctools && \
|
|
|
|
|
patch -p1 < $($(package)_patch_dir)/no_fixup_chains.patch
|
|
|
|
|
endef
|
|
|
|
|
else
|
|
|
|
|
define $(package)_preprocess_cmds
|
|
|
|
|
cp -f $(BASEDIR)/config.guess $(BASEDIR)/config.sub cctools && \
|
|
|
|
|
patch -p1 < $($(package)_patch_dir)/no_fixup_chains.patch
|
|
|
|
|
endef
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
define $(package)_config_cmds
|
|
|
|
|
$($(package)_autoconf)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define $(package)_build_cmds
|
|
|
|
|
$(MAKE)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define $(package)_stage_cmds
|
|
|
|
|
$(MAKE) DESTDIR=$($(package)_staging_dir) install
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define $(package)_postprocess_cmds
|
|
|
|
|
rm -rf share
|
|
|
|
|
endef
|
