aboutsummaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)Author
2016-04-05build: Remove unnecessary executables from gitian releaseWladimir J. van der Laan
This removes the following executables from the binary gitian release: - test_bitcoin-qt[.exe] - bench_bitcoin[.exe] @jonasschnelli and me discussed this on IRC a few days ago - unlike the normal `bitcoin_tests` which is useful to see if it is safe to run bitcoin on a certain OS/environment combination, there is no good reason to include these. Better to leave them out to reduce the download size. Sizes from the 0.12 release: ``` 2.4M bitcoin-0.12.0/bin/bench_bitcoin.exe 22M bitcoin-0.12.0/bin/test_bitcoin-qt.exe ``` Github-Pull: #7776 Rebased-From: f063863d1fc964aec80d8a0acfde623543573823
2016-03-30bump version to 0.12.1Wladimir J. van der Laan
2016-01-27release: Add security/export checks to gitian and fix current failuresCory Fields
- fix parsing of BIND_NOW with older readelf - add _IO_stdin_used to ignored exports For details see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634261#109 - add check-symbols and check-security make targets These are not added to the default checks because some of them depend on release-build configs. - always link librt for glibc back-compat builds glibc absorbed clock_gettime in 2.17. librt (its previous location) is safe to link in anyway for back-compat. Fixes #7420 - add security/symbol checks to gitian Github-Pull: #7424 Rebased-From: cd27bf51e06a8d79790a631696355bd05751b0aa 475813ba5b208eb9a5d027eb628a717cc123ef4f f3d3eaf78eb51238d799d8f20a585550d1567719 a8ce872118c4807465629aecb9e4f3d72d999ccb a81c87fafce43e49cc2307947e3951b84be7ca9a
2016-01-18Update license year range to 2016Prayag Verma
Conflicts: configure.ac Github-Pull: #7363 Rebased-From: bd34174ebca239e6796f0eb2015ddc2f218aac3c
2015-12-03Bump version to 0.12.0Wladimir J. van der Laan
Bump version from 0.11.99 to 0.12.0 so that we don't forget to do this when rc1 is released.
2015-11-13Update key.cpp to new secp256k1 APIPieter Wuille
2015-11-09build: Split hardening/fPIE options outCory Fields
This allows for fPIE to be used selectively.
2015-11-04build: If both Qt4 and Qt5 are installed, use Qt5Wladimir J. van der Laan
If both Qt4 and Qt5 development headers are installed, use Qt5. Building against Qt5 should be encouraged as that is where active development happens.
2015-10-29Merge pull request #6870Wladimir J. van der Laan
040c0ea Init: Cleanup error and warning strings (MarcoFalke) 6782f58 [trivial] Latest config.guess (MarcoFalke) bf68191 [trivial] rpcnet: fix typo (MarcoFalke) 95f4291 [trivial] Rewrite help text for feature enabled by default (MarcoFalke)
2015-10-23Add config option to enable extended RPC tests for code coveragedexX7
When using lcov to gather code coverage data, the configuration option `--enable-extended-rpc-tests` may be used to enable extended RPC tests.
2015-10-23Require Python for RPC tests, when using lcovdexX7
Because Python is (going to be) used to run the RPC tests, when gathering coverage data with lcov, it is explicitly checked, whether Python is really available.
2015-10-22[trivial] Rewrite help text for feature enabled by defaultMarcoFalke
c.f #6748
2015-10-06Merge pull request #6733Wladimir J. van der Laan
7072c54 Support very-fast-running benchmarks (Gavin Andresen) 535ed92 Simple benchmarking framework (Gavin Andresen)
2015-10-06Merge pull request #6743Wladimir J. van der Laan
dd28089 autotools: move checking for zmq library to common area in configure.ac (Johnathan Corgan)
2015-10-05Merge pull request #6744Wladimir J. van der Laan
bb24835 build: disable -Wself-assign (Wladimir J. van der Laan)
2015-10-05Merge pull request #6748Wladimir J. van der Laan
9ee5ac8 Rewrite help texts for features enabled by default. (Pavel Janík)
2015-10-05build: Remove unnecessary chmods after #6616Wladimir J. van der Laan
Don't chmod a repository-included file in the configure script, and `tests_config.py` is a module that doesn't need to be executable.
2015-10-03autotools: move checking for zmq library to common area in configure.acJohnathan Corgan
* Fixes #6679 * Tested with --disable-zmq * Tested with and without pkgconfig * Tested with and without zmq installed Signed-off-by: Johnathan Corgan <johnathan@corganlabs.com>
2015-10-02Rewrite help texts for features enabled by default.Pavel Janík
2015-10-01Merge pull request #6616Wladimir J. van der Laan
5467820 Migrated rpc-tests.sh to all python rpc-tests.py (ptschip)
2015-10-01Merge pull request #6739Wladimir J. van der Laan
96106f0 [Trivial] start the help texts with lowercase (paveljanik)
2015-10-01Migrated rpc-tests.sh to all python rpc-tests.pyptschip
1) created rpc-tests.py 2) deleted rpc-tests.sh 3) travis.yml points to rpc-tests.py 4) Modified Makefile.am 5) Updated README.md 6) Added tests_config.py and deleted tests-config.sh 7) Modified configure.ac with script to set correct path in tests_config.py
2015-10-01build: disable -Wself-assignWladimir J. van der Laan
Prevent these warnings in clang 3.6: ./serialize.h:96:9: warning: explicitly assigning value of variable of type 'uint64_t' (aka 'unsigned long') to itself [-Wself-assign] obj = (obj); ~~~ ^ ~~~
2015-10-01Merge pull request #6732Wladimir J. van der Laan
a3874c7 doc: no longer require use of openssl in OpenBSD build guide (Wladimir J. van der Laan) 5978388 build: remove libressl check (Wladimir J. van der Laan)
2015-10-01build: remove libressl checkWladimir J. van der Laan
Now that BIP66 passed, OpenSSL is no longer directly part of the consensus. What matters is that DER signatures are correctly parsed, and secp256k1 crypto is implemented correctly (as well as the other functions we use from OpenSSL, such as random number generation) This means that effectively, using LibreSSL is not a larger risk than using another version of OpenSSL. Remove the specific check for LibreSSL. Includes the still-relevant part of #6729: make sure CHECK_HEADER is called using the right CXXFLAGS, not CFLAGS (as AC_LANG is c++).
2015-10-01[Univalue] add univalue over subtreeJonas Schnelli
similar to secp256k1 include and compile univalue over a subtree
2015-09-30Simple benchmarking frameworkGavin Andresen
Benchmarking framework, loosely based on google's micro-benchmarking library (https://github.com/google/benchmark) Wny not use the Google Benchmark framework? Because adding Even More Dependencies isn't worth it. If we get a dozen or three benchmarks and need nanosecond-accurate timings of threaded code then switching to the full-blown Google Benchmark library should be considered. The benchmark framework is hard-coded to run each benchmark for one wall-clock second, and then spits out .csv-format timing information to stdout. It is left as an exercise for later (or maybe never) to add command-line arguments to specify which benchmark(s) to run, how long to run them for, how to format results, etc etc etc. Again, see the Google Benchmark framework for where that might end up. See src/bench/MilliSleep.cpp for a sanity-test benchmark that just benchmarks 'sleep 100 milliseconds.' To compile and run benchmarks: cd src; make bench Sample output: Benchmark,count,min,max,average Sleep100ms,10,0.101854,0.105059,0.103881
2015-09-30[Trivial] start the help texts with lowercasepaveljanik
2015-09-29zmq: require version 4.x or newer of libzmqJohnathan Corgan
Signed-off-by: Johnathan Corgan <johnathan@corganlabs.com>
2015-09-16configure.ac: Revert autotools-auto-updated 2.69 autoconf requirementJeff Garzik
Also, autotools reformatted the AC_ARG_ENABLE erroneously as well.
2015-09-16Merge pull request #6317Jeff Garzik
2015-09-16Add ZeroMQ support. Notify blocks and transactions via ZeroMQJeff Garzik
Continues Johnathan Corgan's work. Publishing multipart messages Bugfix: Add missing zmq header includes Bugfix: Adjust build system to link ZeroMQ code for Qt binaries
2015-09-02build: build-system changes for libeventWladimir J. van der Laan
2015-07-31build: fix libressl detectionCory Fields
Checking libcrypto for a function after we've already found a (possibly different) libcrypto is not what we want to do here. pkg-config might've found a cross lib while AC_CHECK_LIB may find a different or native one. Run a link-test against the lib that's already been found instead.
2015-07-15configure --enable-debug changesGavin Andresen
Three changes to how configure --enable-debug behaves: 1. Preserve user-passed CXXFLAGS/CFLAGS 2. Compile with -DDEBUG_LOCKORDER 3. Add -DDEBUG -DDEBUG_LOCKORDER to CPPFLAGS (since they are preprocessor options)
2015-06-21build: Remove -DBOOST_SPIRIT_THREADSAFEWladimir J. van der Laan
Now that boost spirit is no longer used, `-DBOOST_SPIRIT_THREADSAFE` doesn't need to be passed to the compiler anymore.
2015-06-10Merge pull request #6244Wladimir J. van der Laan
a5a81f7 configure: Detect (and reject) LibreSSL (Luke Dashjr)
2015-06-07Add an alternate location of endian.h headerAndriy Voskoboinyk
2015-06-06configure: Detect (and reject) LibreSSLLuke Dashjr
2015-06-01build: disable optional use of gmp in internal secp256k1 buildWladimir J. van der Laan
Until secp256k1 is used for verification there is no reason for Bitcoin Core's secp256k1 to link against gmp, even if available. Pass a flag to configure to override the bignum implementation. This fixes a crash at runtime on ppc64 reported by @gmaxwell.
2015-06-01Now that 0.11 has been branched, master is 0.11.99Wladimir J. van der Laan
... in preparation for 0.12
2015-05-14build: make libboost_chrono mandatoryCory Fields
previously it was only used with certain boost versions. Now all versions require it.
2015-05-02change AC_PACKAGE_BUGREPORT from info@bitcoin.org to github issue tracker URLJonas Schnelli
Mentioned by wumpus: http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/05/02#l1430543664 Details here: http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Initializing-configure.html
2015-03-06build: Endian compatibilityWladimir J. van der Laan
- Detect endian instead of stopping configure on big-endian - Add `byteswap.h` and `endian.h` header for compatibility with Windows and other operating systems that don't come with them - Update `crypto/common.h` functions to use compat endian header
2015-03-03Merge pull request #5819Wladimir J. van der Laan
d23b0a2 depends: always use static qt5 for linux (Cory Fields) 3448b13 build: fix typo in configure help (Cory Fields) c95ac83 gitian: fix x86_64 build with static libstdc++ (Cory Fields) 0671516 build: change reduce exports/static libstdc++ options for gitian and travis (Cory Fields) aa36730 build: remove libstdc++ backwards-compat (Cory Fields) 3ee028f build: disable reduced exports by default (Cory Fields)
2015-03-02keys: remove libsecp256k1 verification until it's actually supportedCory Fields
This was added a while ago for testing purposes, but was never intended to be used. Remove it until upstream libsecp256k1 decides that verification is stable/ready.
2015-02-23build: fix typo in configure helpCory Fields
2015-02-23build: remove libstdc++ backwards-compatCory Fields
Backwards-compatibility for libstdc++ is not limited to straightforward abi changes. Symbol visibility also needs to be taken into consideration, and that really can't be addressed simply. Instead, just static-link libstdc++ for backwards-compat.
2015-02-23build: disable reduced exports by defaultCory Fields
This is really a packager's option. While it's helpful to encourage devs to test this option for daily builds, it's not reliable in several real-world use-cases. Some older libstdc++ runtimes (freebsd 9, debian wheezy, for example) fail to properly catch exceptions due to mismatched type_info. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19664 for more info.
2015-01-21Remove custom pkg.m4 script.randy-waterhouse
generated by cgit v1.2.3 (git 2.26.2) at 2024-07-03 04:51:59 +0000