aboutsummaryrefslogtreecommitdiff
path: root/src/compat
Commit message (Collapse)AuthorAgeFilesLines
* Increment MIT Licence copyright header year on files modified in 2016isle29832016-12-312-2/+2
| | | | | | Edited via: $ contrib/devtools/copyright_header.py update .
* Uses built-in byte swap if available (Apple) and if bswap_XX is undefined.Karl-Johan Alm2016-12-171-0/+19
| | | | Defers to pre-defined version if found (e.g. protobuf). For protobuf case, the definitions are identical and thus include order should not affect results.
* [copyright] copyright header style uniformisle29832016-11-062-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Three categories of modifications: 1) 1 instance of 'The Bitcoin Core developers \n', 1 instance of 'the Bitcoin Core developers\n', 3 instances of 'Bitcoin Core Developers\n', and 12 instances of 'The Bitcoin developers\n' are made uniform with the 443 instances of 'The Bitcoin Core developers\n' 2) 3 instances of 'BitPay, Inc\.\n' are made uniform with the other 6 instances of 'BitPay Inc\.\n' 3) 4 instances where there was no '(c)' between the 'Copyright' and the year where it deviates from the style of the local directory.
* Bump copyright headers to 2015MarcoFalke2015-12-131-1/+1
|
* Add an alternate location of endian.h headerAndriy Voskoboinyk2015-06-071-0/+2
|
* build: Endian compatibilityWladimir J. van der Laan2015-03-062-0/+241
| | | | | | | | - 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
* build: remove libstdc++ backwards-compatCory Fields2015-02-231-94/+0
| | | | | | | | 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.
* Added "Core" to copyright headerssandakersmann2014-12-196-6/+6
| | | | | Github-Pull: #5494 Rebased-From: 15de949bb9277e442302bdd8dee299a8d6deee60
* Check for strnlen and provide it if it is not found.Pavel Janík2014-11-241-0/+18
|
* Fix all header definesPavel Janík2014-11-031-3/+3
|
* update license of compat and cryptoPhilip Kaufmann2014-09-295-5/+7
| | | | | | - change license to be just MIT for all files in compat and crypto - also add missing header end comments - ensure default header include style
* Apply clang-format on crypto/* and compat/*Pieter Wuille2014-09-254-33/+28
|
* libc-compat: add new symbol that's now neededCory Fields2014-08-081-0/+2
|
* build: fix build weirdness after 54372482.Cory Fields2014-06-232-2/+2
| | | | | | | | | | | | | bitcoin-config.h moved, but the old file is likely to still exist when reconfiguring or switching branches. This would've caused files to not rebuild correctly, and other strange problems. Make the path explicit so that the old one cannot be found. Core libs use config/bitcoin-config.h. Libs (like crypto) which don't want access to bitcoin's headers continue to use -Iconfig and #include bitcoin-config.h.
* small cleanup in src/compat .h and .cppPhilip Kaufmann2014-06-215-29/+58
| | | | | | - add license header - fix include guards - fix indentation
* sanity: add libc/stdlib sanity checksCory Fields2014-06-163-0/+129
| | | | | These are meant to test our back-compat stubs, but they are enabled for all builds for the sake of consistency.
* build: add symbol for upcoming gcc 4.9's libstdc++Cory Fields2014-04-111-0/+7
|
* build: add glibc/libstdc++ back-compat stubsCory Fields2014-04-102-0/+99
glibc/libstdc++ have added new symbols in later releases. When running a new binary against an older glibc, the run-time linker is unable to resolve the new symbols and the binary refuses to run. This can be fixed by adding our own versions of those functions, so that the build-time linker does not emit undefined symbols for them. This enables our binary releases to work on older Linux distros, while not incurring the downsides of a fully static binary.