6d868a2c65
Some error reports are misleading on some recent versions of gcc because it goes on to build for a very long time after it meets an error. Not only this makes it hard to scroll back to the beginning of the error, but it also hides the cause of the error when it's prominently printed in a "#error" statement. This typically happens when building with QUIC and without OPENSSL where there can be 4 pages of unknown types and such errors after the "Must define USE_OPENSSL" suggestion. The flag -Wfatal-errors serves exactly this purpose, to stop after the first error, and it's supported on all the compilers we support, so let's enable this now.
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)