mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 13:51:26 +02:00
70c268b4da
We've had libatomic enabled on arm and aarch64 for some Raspberry PI while usually it's not needed, but it was a bit arbitrary and in issue #1455 it was reported that RISCV requires it for single-byte atomics. This changes the approach to detect the explicit requirement of external functions for the builtins, as reported with *_LOCK_FREE=1. If any of the atomics requires libatomic, it will be used. Older compilers do not report any such atomic as they use sync_* instead and will not match it nor include libatomic (which usually is not present there). On x86, the rules depend on -march. i386 uses LOCK_FREE=1 for all of them. i486 uses it only for the 8-byte CAS and i586 doesn't require it at all. For this reason, the build flags are used during the test. This was tested with armv7, aarch64, mips, riscv, i
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)