summaryrefslogtreecommitdiff
path: root/m4
Commit message (Collapse)AuthorAgeFilesLines
* ESNI: initial build/setupNiall2019-10-021-1/+37
| | | | Closes #4011
* configure: fix --disable-code-coverageJan Chren2019-07-091-2/+1
| | | | | | | | This fixes the case when --disable-code-coverage supplied to ./configure would result in coverage="yes" being set. Closes #4099 Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
* configure/cmake: check for if_nametoindex()Daniel Stenberg2019-05-221-0/+113
| | | | | | | | - adds the check to cmake - fixes the configure check to work for cross-compiled windows builds Closes #3917
* configure: detect getsockname and getpeername on windows tooDaniel Stenberg2019-05-211-0/+195
| | | | | | | | | | | Made detection macros for these two functions in the same style as other functions possibly in winsock in the hope this will work better to detect these functions when cross-compiling for Windows. Follow-up to e91e4816123 Fixes #3913 Closes #3915
* configure: add --with-amisslChris Young2019-03-151-0/+50
| | | | | | | | | | AmiSSL is an Amiga native library which provides a wrapper over OpenSSL. It also requires all programs using it to use bsdsocket.library directly, rather than accessing socket functions through clib, which libcurl was not necessarily doing previously. Configure will now check for the headers and ensure they are included if found. Closes #3677
* configure: remove the unused fdopen macroDaniel Stenberg2019-02-221-86/+0
| | | | | | and the two remaining #ifdefs for it Closes #3600
* configure: rewrite --enable-code-coverageDaniel Stenberg2019-01-262-265/+41
| | | | | | | | | The previously used ax_code_coverage.m4 is not license compatible and must not be used. Reported-by: William A. Rowe Jr Fixes #3497 Closes #3499
* curl-compilers.m4: check for __ibmxl__ to detect xlclangDaniel Stenberg2019-01-161-2/+2
| | | | | | | | Follow-up to 2fa0d57e2e3. The __xlc__ symbol is only defined there if a particular flag is used for legacy macros. Fixes #3474 Closes #3479
* curl-compilers.m4: detect xlclangDaniel Stenberg2019-01-151-2/+11
| | | | | | | | | Since it isn't totally clang compatible, we detect this IBM clang front-end and if detected, avoids some clang specific magic. Reported-by: Kees Dekker Fixes #3474 Closes #3476
* configure: Fix typo in commentDaniel Gustafsson2018-11-211-1/+1
|
* configure: s/AC_RUN_IFELSE/CURL_RUN_IFELSEDaniel Stenberg2018-09-262-10/+10
| | | | | | | fix a few leftovers Fixes #3006 Closes #3049
* whitespace fixesViktor Szakats2018-09-2312-13/+0
| | | | | | | | | | | - replace tabs with spaces where possible - remove line ending spaces - remove double/triple newlines at EOF - fix a non-UTF-8 character - cleanup a few indentations/line continuations in manual examples Closes https://github.com/curl/curl/pull/3037
* Enable more GCC warningsMarcel Raad2018-08-211-1/+15
| | | | | | | | | | | | | | This enables the following additional warnings: -Wold-style-definition -Warray-bounds=2 instead of the default 1 -Wformat=2, but only for GCC 4.8+ as Wno-format-nonliteral is not respected for older versions -Wunused-const-variable, which enables level 2 instead of the default 1 -Warray-bounds also in debug mode through -ftree-vrp -Wnull-dereference also in debug mode through -fdelete-null-pointer-checks Closes https://github.com/curl/curl/pull/2747
* curl-compilers: enable -Wimplicit-fallthrough=4 for GCCMarcel Raad2018-08-211-0/+1
| | | | | | | | This enables level 4 instead of the default level 3, which of the currently used comments only allows /* FALLTHROUGH */ to silence the warning. Closes https://github.com/curl/curl/pull/2747
* curl-compilers: enable -Wbad-function-cast on GCCMarcel Raad2018-08-211-0/+1
| | | | | | | This warning used to be enabled only for clang as it's a bit stricter on GCC. Silence the remaining occurrences and enable it on GCC too. Closes https://github.com/curl/curl/pull/2747
* curl-confopts.m4: fix typo from ed224f23d5bebDaniel Stenberg2018-06-151-1/+1
| | | | | Fixes my local configure to detect a custom installed c-ares without pkgconfig.
* configure: use pkg-config for c-ares detectionDaniel Stenberg2018-06-141-7/+32
| | | | | | | | | First check if there's c-ares information given as pkg-config info and use that as first preference. Reported-by: pszemus on github Fixes #2203 Closes #2658
* configure: add missing m4/ax_compile_check_sizeof.m4Daniel Stenberg2018-05-221-0/+115
| | | | follow-up to mistake in 6876ccf90b4
* configure: replace AC_TRY_RUN with CURL_RUN_IFELSEDaniel Stenberg2018-05-211-1/+2
| | | | | | | | ... and export LD_LIBRARY_PATH properly. This is a follow-up from 2d4c215. Fixes #2586 Reported-by: Bernhard Walle
* configure: put CURLDEBUG and DEBUGBUILD in lib/curl_config.hFrank Gevaerts2018-05-042-10/+4
| | | | | | | | | They are removed from the compiler flags. This ensures that make dependency tracking will force a rebuild whenever configure --enable-debug or --enable-curldebug changes. Closes #2548
* configure: keep LD_LIBRARY_PATH changes localDaniel Stenberg2018-04-161-1/+17
| | | | | | | | | | ... only set it when we actually have to run tests to reduce its impact on for example build commands etc. Fixes #2490 Closes #2492 Reported-by: Dmitry Mikhirev
* build: add picky compiler warning flags for gcc 6 and 7Eric Gallager2018-04-071-0/+17
|
* curl-openssl.m4: fix spelling [ci skip]Viktor Szakats2018-03-121-1/+1
|
* curl-openssl.m4: Fix version check for OpenSSL 1.1.1Jay Satiro2018-02-241-1/+10
| | | | | | | | | | - Add OpenSSL 1.1.1 to the header/library version lists. - Detect OpenSSL 1.1.1 library using its function ERR_clear_last_mark, which was added in that version. Prior to this change an erroneous header/library mismatch was caused by lack of OpenSSL 1.1.1 detection. I tested using openssl-1.1.1-pre1.
* configure: set PATH_SEPARATOR to colon for PATH w/o separatorDaniel Stenberg2018-01-301-7/+5
| | | | | | | | | | | | | | | | | The logic tries to figure out what the path separator in the $PATH variable is, but if there's only one directory in the $PATH it fails. This change make configure *guess* on colon instead of erroring out, simply because that is probably the more common character. PATH_SEPARATOR can always be set by the user to override the guessing. (tricky bug to reproduce, as in my case for example the configure script requires binaries in more than one directory so passing in a PATH with a single dir fails.) Reported-by: Earnestly on github Fixes #2202 Closes #2265
* configure: use -Wno-varargs on clang 3.9[.X] debug buildsDaniel Stenberg2017-09-081-1/+6
| | | | ... to avoid a clang bug
* m4/curl-compilers.m4: use proper quotes around string, not backticksDaniel Stenberg2017-08-161-1/+1
| | | | | | ... when setting clang version to assume 3.7 Caused a lot of "integer expression expected" warnings by configure.
* curl-confopts.m4: fix --disable-threaded-resolverJakub Zakrzewski2017-08-151-4/+4
| | | | Closes https://github.com/curl/curl/issues/1784
* configure: use the threaded resolver backend by default if possibleDaniel Stenberg2017-08-101-5/+5
| | | | Closes #1647
* ax_code_coverage.m4: update to latest versionMarcel Raad2017-08-081-69/+114
| | | | | | | This updates the script to aad5ad5fedb306b39f901a899b7bd305b66c418d from August 01, 2017. Notably, this removes the lconv version whitelist. Closes https://github.com/curl/curl/pull/1716
* curl-compilers.m4: disable warning spam with Cygwin's clangMarcel Raad2017-07-101-1/+9
| | | | | | | | | | | | When building with Cygwin or MinGW, libtool uses a wrapper executable instead of a wrapper script [1], which is written in C and throws missing-variable-declarations warnings. Don't enable these warnings on Cygwin and MinGW in order to avoid warnings for every executable built, which spams the test suite output when using Cygwin's clang. [1] https://www.gnu.org/software/libtool/manual/html_node/Wrapper-executables.html Closes https://github.com/curl/curl/pull/1665
* curl-compilers.m4: fix unknown-warning-option on Apple clangMarcel Raad2017-06-241-1/+10
| | | | | | | | | | | | | | | | | | Since 5598b0bd63f690c151074494ce47ef872f004ab4, clang -v is used to detect the clang version. The version number was expected to come after the word "version". For Apple clang, this doesn't work as it has its own versioning scheme. The version number is now first searched after the string "based on LLVM". This works for Apple clang before version 7, and also for e.g. Ubuntu's clang up to version 3.7. If it's not found and the version string contains "Apple LLVM version", clang version 3.7 is assumed, which is the version that comes with Xcode 7. Otherwise, the version number is still expected after the word "version", which works for very old Apple clang versions. Ref: https://trac.macports.org/wiki/XcodeVersionInfo Fixes https://github.com/curl/curl/issues/1606 Closes https://github.com/curl/curl/pull/1607
* curl-compilers.m4: enable comma clang warningMarcel Raad2017-06-161-0/+5
| | | | | | | It usually warns when using commas instead of semicolons or other operators by accident. Closes https://github.com/curl/curl/pull/1578
* curl-compilers.m4: enable missing-variable-declarations clang warningMarcel Raad2017-06-161-0/+5
| | | | | | It usually warns when forgetting to declare TU-local variables static. Closes https://github.com/curl/curl/pull/1578
* curl-compilers.m4: enable double-promotion warningMarcel Raad2017-06-161-0/+10
| | | | | | | Enable -Wdouble-promotion for both GCC and clang. It warns on implicit promotion from float to double. Closes https://github.com/curl/curl/pull/1578
* curl-compilers.m4: enable vla warning for clangMarcel Raad2017-06-161-0/+5
| | | | | | | Previously, that warning was only implicitly active in C90 mode. Enable it unconditionally as already done for GCC. Closes https://github.com/curl/curl/pull/1578
* build: provide easy code coverage measuringDaniel Stenberg2017-06-021-0/+219
| | | | Closes #1528
* curl-compilers.m4: escape square brackets in regexMarcel Raad2017-06-011-1/+1
| | | | | Otherwise, they are removed in the final configure file. Also changed sed to "$SED" like in most other calls in this file.
* curl-compilers.m4: fix compiler_num for clangMarcel Raad2017-06-011-1/+1
| | | | | | | | | "clang -dumpversion" always returns "4.2.1", the GCC version that clang was initially compatible to. Use "clang -v" instead, which returns the actual clang version. Fixes https://github.com/curl/curl/issues/1522 Closes https://github.com/curl/curl/pull/1523
* curl-compilers.m4: enable -Wshift-sign-overflow for clangMarcel Raad2017-05-311-0/+5
| | | | | | | | clang 2.9+ supports -Wshift-sign-overflow, which warns about undefined behavior on signed left shifts when shifting by too many places. Ref: https://github.com/curl/curl/issues/1516 Closes https://github.com/curl/curl/pull/1517
* configure: stop prepending to LDFLAGS, CPPFLAGSJay Satiro2017-04-251-2/+2
| | | | | | | | - Change prepends to appends because user's LDFLAGS and CPPFLAGS should always come first so they're searched before ours. Bug: https://github.com/curl/curl/issues/1420 Reported-by: Helmut K. C. Tessarek
* curl-compilers.m4: accept -Og and -Ofast GCC flagsMarcel Raad2017-04-241-1/+1
| | | | | | | | | | | | -Og, introduced in GCC 4.8, optimizes for debugging experience. -Ofast, introduced in GCC 4.7, builds on -O3 and enables further optimizations breaking strict standards compliance. When specified in CFLAGS, these were always overridden by -O0 or -O2. Fix this by adding them to flags_opt_all. Ref: https://gcc.gnu.org/onlinedocs/gcc-4.8.0/gcc/Optimize-Options.html Ref: https://github.com/curl/curl/pull/1404#issuecomment-296401570 Closes https://github.com/curl/curl/pull/1440
* curl-compilers.m4: turn implicit function declarations into errorsMarcel Raad2017-04-151-2/+5
| | | | | | | | | | | | | This adds -Werror-implicit-function-declaration for GCC 2.95+ so that these errors are visible at the point where they occur instead of only at link time. Implicit function declarations are illegal in C99 and C++ anyway, and the same warning has been turned into an error for ICC in commit 3072c5b8a127057aa922b7c51051bbb4a630b091. Ref: https://gcc.gnu.org/onlinedocs/gcc-2.95.2/gcc_2.html#SEC8 Ref: https://curl.haxx.se/mail/lib-2017-04/0001.html Closes https://github.com/curl/curl/pull/1419
* spelling fixesklemens2017-03-263-7/+7
| | | | Closes #1356
* configure: fix for --enable-pthreadsJay Satiro2017-03-021-4/+0
| | | | | | | Better handle options conflicts that can occur if --enable-pthreads. Bug: https://github.com/curl/curl/pull/1295 Reported-by: Marc-Antoine Perennou
* s/cURL/curlDaniel Stenberg2016-11-071-1/+1
| | | | | | We're mostly saying just "curl" in lower case these days so here's a big cleanup to adapt to this reality. A few instances are left as the project could still formally be considered called cURL.
* configure/CURL_CHECK_FUNC_POLL: disable poll completely on macDaniel Stenberg2016-10-181-1/+4
| | | | | | ... so that the same libcurl build easier can run on any version. Follow-up to issue #1057
* configure: detect the broken poll() in macOS 10.12Daniel Stenberg2016-10-111-3/+19
| | | | Fixes #1057
* curl-compilers.m4: improve detection of GCC's -fvisibility= flagKamil Dudka2016-06-211-2/+2
| | | | | | | | | | Some builds of GCC produce output on both stdout and stderr when --help --verbose is used. The 2>&1 redirection caused them to be arbitrarily interleaved with each other because of stream buffering. Consequently, grep failed to match the fvisibility= string in the mixed output, even though the string was present in GCC's standard output. This led to silently disabling symbol hiding in some builds of curl.
* configure: ac_cv_ -> curl_cv_ for write-only varsIrfan Adilovic2016-04-211-103/+103
| | | | | | | | | | | | | | | | | | | These configure vars are modified in a curl-specific way but never evaluated or loaded from cache, even though they are designated as _cv_. We could either implement proper AC_CACHE_CHECKs for them, or remove them completely. Fixes #603 as ac_cv_func_gethostbyname is no longer clobbered, and AC_CHECK_FUNC(gethostbyname...) will no longer spuriously succeed after the first configure run with caching. `ac_cv_func_strcasecmp` is curious, see #770. `eval "ac_cv_func_$func=yes"` can still cause problems as it works in tandem with AC_CHECK_FUNCS and then potentially modifies its result. It would be best to rewrite this test to use a new CURL_CHECK_FUNCS macro, which works the same as AC_CHECK_FUNCS but relies on caching the values of curl_cv_func_* variables, without modifiying ac_cv_func_*.
View Lorry Controller Status