aboutsummaryrefslogtreecommitdiff
path: root/depends/patches
AgeCommit message (Collapse)Author
2018-03-06depends: biplist 1.0.3fanquake
2018-03-05depends: patch pthread_set_name_np out of zeromqCory Fields
2018-03-05[Depends] Fix Qt build with Xcode 9.2fanquake
2018-02-13Delete mac_alias patchDouglas Roark
The patch Bitcoin Core has been maintaining for mac_alias was pulled by the mac_alias maintainer in commit 4f31cb084c1c6a8626128b0b00842020b6db9037. Delete the patch and remove the patch from the depends system. Note that this PR won't be complete until a new version of mac_alias containing the path has been released, and the depends system is updated to reflect the new version.
2017-11-29depends: fix zmq build with mingw < 4.0Cory Fields
2017-11-29[depends] ZeroMQ 4.2.2fanquake
2017-10-07[depends] native_mac_alias 2.0.6fanquake
2017-01-28qt: fix build with zlib for targetCory Fields
This contains a few hacks very specific to Qt's buildsystem. These can be reverted once we split the build between native and target builds. Qt's build contains a circular dependency when not using a system zlib. By far the easiest fix is to switch to a system zlib, rather than Qt's own. However, that confuses Qt's cross build which assumes that when using a system zlib, it should also find a system (native) zlib for native tools. The build breaks if that zlib is not present. To solve this: 1. Always use a system zlib rather than the one provided by qt 2. Set force_bootstrap, which instructs the build tools to be built as though we're cross-compiling (build != target) 3. For build tools, use qt's internal zlib so that a native zlib is not required. Step 3 means that if any zlib headers are found by the native build, it will confuse Qt's internal zlib build. So we also need to make sure that the target headers/libs aren't found. To do so, specify that our cflags/cxxflags/cppflags/ldflags only apply for non-host builds.
2017-01-19depends: qt: disable printer for all platforms, not just osxCory Fields
This also fixes the native osx build.
2017-01-14depends: use new variable layout for qt sdkCory Fields
2017-01-14[depends] Qt 5.7.1fanquake
2017-01-04[depends] libevent 2.1.7rcfanquake
2016-09-29Merge #8730: depends: Add libevent compatibility patch for windowsWladimir J. van der Laan
64047f8 depends: Add libevent compatibility patch for windows (Wladimir J. van der Laan)
2016-09-27[depends] Fix Qt compilation with Xcode 8fanquake
2016-09-14depends: Add libevent compatibility patch for windowsWladimir J. van der Laan
Add a patch that seems to be necessary for compatibilty of libevent 2.0.22 with recent mingw-w64 gcc versions (at least GCC 5.3.1 from Ubuntu 16.04). Without this patch the Content-Length in the HTTP header ends up as `Content-Length: zu`, causing communication between the RPC client and server to break down. See discussion in #8653. Source: https://sourceforge.net/p/levent/bugs/363/ Thanks to @sstone for the suggestion.
2016-09-01Remove unused Qt 4.6 patch.Doug
Core no longer supports Qt 4. Therefore, the STL fix patch isn't needed.
2016-07-21[depends] ZeroMQ 4.1.5fanquake
2016-07-19build: fix non-deterministic biplistCory Fields
The non-deterministic ordering produced by biplist ends up in the .DS_Store file that is included in the OSX dmg.
2016-06-17Fix bitcoin_qt.m4 and fix-xcb-include-order.patchJonas Schnelli
2016-04-21depends: mac deploy Py3 compatibilityWladimir J. van der Laan
This fixes the gitian MacOSX build, it was broken in #7723. The patch to `native_mac_alias` should probably make it upstream.
2016-03-01[depends] Delete unused patchesMarcoFalke
Superseded by 4bdad99f5000539dcf03ddc92c142fa6deb44c01
2015-11-16depends: qt PIDLIST_ABSOLUTE patchWladimir J. van der Laan
Remove sed-based qt PIDLIST_ABSOLUTE workaround, replace by a patch that works for both old (such as used by Travis and Ubuntu Precise) and new mingw (Ubuntu Trusty).
2015-09-03libevent: Windows reuseaddr workaround in dependsCory Fields
Make it possible to reuse sockets. This is necessary to make the RPC tests work in WINE.
2015-07-27fixup: qt 5.5 snuck in another module that needs path hand-holdingCory Fields
2015-07-23depends: bump to qt 5.5Cory Fields
2015-06-13depends: fix Boost 1.55 build on GCC 5Jacob Welsh
Boost assumes variadic templates are always available in GCC 4.4+, but they aren't since we don't build with -std=c++11. This applies the patch that fixed the issue in boost 1.57: https://github.com/boostorg/config/commit/eec808554936ae068b23df07ab54d4dc6302a695 See also: https://svn.boost.org/trac/boost/ticket/10500
2015-03-16depends: fix a static qt5 crash when using certain versions of libxcbCory Fields
See here for background: https://bugreports.qt.io/browse/QTBUG-34748 libxcb temporarily had an abi breakage which caused crashes when qt was compiled against a non-compatible version. Building qt with -qt-xcb should have shielded us from this issue, except that incompatible headers were used when building qt's wrapper. Make sure those headers aren't picked up by qt's build. Details: qt's build adds a wrapper around the xcb libs when -qt-xcb is used. This is done to avoid having to link to a handful of different libs, which may not be api/abi stable. This build depends on include-order, so that its files are found before the real libxcb headers. Our build (for other reasons related to qt's complicated build-system) injects our prefix into CXXFLAGS. Because libxcb is found in this path, that reverses the include-order, negating the purpose of the wrapper. To fix, libxcb's includes are simply moved to a subdir. pkg-config ensures that they're still found properly when needed. To make things even more interesting, this behavior in qt's .pro files is broken: INCLUDEPATH += $$QMAKE_CFLAGS_XCB The INCLUDEPATH variable is processed by qmake which automatically prefixes each entry with "-I". The QMAKE_CFLAGS_XCB variable comes from pkg-config and already contains -I, making the path look like "-I-I/path/to/xcb/headers". To work around that, CFLAGS/CXXFLAGS are used here rather than INCLUDEPATH.
2015-01-02depends: major upgrade to darwin toolchainCory Fields
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.
2015-01-02depends: osx: fix qt5 build against 10.10 sdkCory Fields
2014-12-04Remove gmp dependency and doc mentionsPieter Wuille
2014-11-19depends: Add a package for qt4.6. Linux uses it by default.Cory Fields
We're not ready to switch to a static qt5 for Linux yet due to missing plugin support. This adds a recipe for building a shared qt4 that we build and link against, but don't distribute. make USE_LINUX_STATIC_QT5=1 can be used to build static qt5 as before.
2014-11-18depends: add gmp packageCory Fields
2014-09-08qt: fix tablet crash. closes #4854.Cory Fields
This backports the relevant parts of: https://codereview.qt-project.org/#/c/82689/
2014-08-08depends: add shared dependency builderCory Fields
See the README's in depends for documentation