atheme/m4/ at master · snowfields.name/atheme

atheme-api-digest-frontend.m4

Avoid year-2038-problem This patch was done while reviewing potential year-2038 issues in openSUSE.

3 weeks ago

atheme-api-random-frontend.m4

RNG: glibc 2.36 supports a secure arc4random(3)

4 years ago

atheme-check-build-requirements.m4

Avoid year-2038-problem This patch was done while reviewing potential year-2038 issues in openSUSE.

3 weeks ago

atheme-conditional-compilation.m4

Build System: Improve handling of enabling and configuring submodules - When performing the libmowgli test, don't pollute CFLAGS / CPPFLAGS / LDFLAGS / LIBS variables. Set library-specific variables, just like the other library tests do This allows us to configure submodules later without having to save the environment variables first - When --with-libmowgli=yes is given, require that pkg-config is available and that it can detect the library, erroring out otherwise - Put the logic for handling enabling and configuring submodules into its own M4 file

5 years ago

atheme-featuretest-cflags.m4

configure: warn on failing to enable various compiler features Also correct the wording of the one previous extant warning. It is automatically probed for by default, so do not imply with the language of the warning that the option was explicitly given.

2 years ago

atheme-featuretest-compiler-sanitizers.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-contrib.m4

modules/contrib/: transition to independent build system Having to duplicate configure tests in all supported Atheme release and development branches, to enable contrib modules to be built reliably on all of our supported platforms, was quickly becoming untenable.

5 years ago

atheme-featuretest-cppflags.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-crypto-benchmarking.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-ecdh-x25519-tool.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-ecdsa-nist256p-tools.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-fhspaths.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-heap-allocator.m4

Update my e-mail address

5 years ago

atheme-featuretest-largenet.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-ldflags.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-legacy-pwcrypto.m4

Update my e-mail address

5 years ago

atheme-featuretest-nls.m4

m4/atheme-featuretest-nls.m4: set USE_NLS to yes when asked to try The AM_GNU_GETTEXT macro relies on this being set to yes, or it does almost nothing and results in it not being available. The ugly AM_NLS macro that I no-oped out in commit 3828bfac7ac27e4593ab did this, which I overlooked when changing it from default-enabled to default-disabled.

2 years ago

atheme-featuretest-reprobuilds.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-featuretest-warnings.m4

m4/atheme-featuretest-warnings.m4: disable two more pointless C++ diagnostics This is not a C++ codebase.

3 weeks ago

atheme-libtest-argon2.m4

Update my e-mail address

5 years ago

atheme-libtest-crack.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-crypt.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-crypto.m4

OpenSSL Digest Frontend: Rewrite HMAC for 3.x compatibility Avoids numerous "is deprecated in OpenSSL 3.0" diagnostics while building libathemecore.

2 years ago

atheme-libtest-dl.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-gcrypt.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-idn.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-ldap.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-math.m4

m4/atheme-libtest-*.m4: correct copy/paste mistake on temporary variable name

5 years ago

atheme-libtest-mbedcrypto.m4

Update my e-mail address

5 years ago

atheme-libtest-mowgli.m4

m4/atheme-libtest-mowgli.m4: add a usability test if using external lib When we are not using the internal libmowgli submodule, do a link test to see if the library is usable, just like we do with the other library tests. This one is fairly extensive, as this codebase makes heavy use of this library.

5 years ago

atheme-libtest-nettle.m4

Update my e-mail address

5 years ago

atheme-libtest-passwdqc.m4

Update my e-mail address

5 years ago

atheme-libtest-pcre.m4

PCRE2 support

3 weeks ago

atheme-libtest-perl.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-libtest-qrencode.m4

m4/atheme-*.m4: use autoconf flow control macros exclusively The AS_IF and AS_CASE macros enable one to write "if" and "case" shell statements in a portable way. They still generate more or less the same output, but code which works better on various obscure platforms. They also allow autoconf to examine the conditional block bodies for macro calls, to ensure those macros are available. This will become more necessary in future versions of autoconf. Also use these to replace an unguarded grep(1) invocation in the Perl library testing macro.

5 years ago

atheme-libtest-socket.m4

Build System: Several small improvements - Don't let autoconf add "-O2 -g" to the CFLAGS variable. Detect optimisations automatically (if sanitizers are not enabled) or explicitly disable them (if they are). Detect debugging flags automatically, preferring DWARF, then GDB, then regular -g as autoconf does. This allows more accurate debugging when supported by the toolchain. Allow debugging symbols to be disabled; enable them by default. - When requested to enable compiler sanitizers, bail out with an error when they cannot be enabled. Update the comment on ATHEME_ENABLE_COMPILER_SANITIZERS to reflect that sanitizers are enabled; rather than just the configure argument given. - Move the logic for testing CFLAGS / CPPFLAGS / LDFLAGS / some combination of them to a dedicated separate file. Tidy up those functions to use the same M4sh coding style as the other files. Explicitly provide a program with both a header and main body when doing compiler and linker tests. Use a unified function and variable name scheme. - Rewrite the compiler sanitizers driver function to use the new combined compiler and linker test logic. - Update the comment in the compiler sanitizers feature file to explain why we are trying to enable LTO (Clang sanitizers require it). - Clean up temporary _SAVED variables at the end of function execution in various feature and library tests. - Remove 2 unsubstituted and unused variables from extra.mk.in. - Support the -Wa,--noexecstack flag to the compiler and linker; enable it by default.

5 years ago

atheme-libtest-sodium.m4

Update my e-mail address

5 years ago

atheme-print-configuration.m4

Update my e-mail address

5 years ago

atheme-submodules.m4

modules/contrib/: transition to independent build system Having to duplicate configure tests in all supported Atheme release and development branches, to enable contrib modules to be built reliably on all of our supported platforms, was quickly becoming untenable.

5 years ago

atheme-toolchain-tests.m4

Build System: Several small improvements - Don't let autoconf add "-O2 -g" to the CFLAGS variable. Detect optimisations automatically (if sanitizers are not enabled) or explicitly disable them (if they are). Detect debugging flags automatically, preferring DWARF, then GDB, then regular -g as autoconf does. This allows more accurate debugging when supported by the toolchain. Allow debugging symbols to be disabled; enable them by default. - When requested to enable compiler sanitizers, bail out with an error when they cannot be enabled. Update the comment on ATHEME_ENABLE_COMPILER_SANITIZERS to reflect that sanitizers are enabled; rather than just the configure argument given. - Move the logic for testing CFLAGS / CPPFLAGS / LDFLAGS / some combination of them to a dedicated separate file. Tidy up those functions to use the same M4sh coding style as the other files. Explicitly provide a program with both a header and main body when doing compiler and linker tests. Use a unified function and variable name scheme. - Rewrite the compiler sanitizers driver function to use the new combined compiler and linker test logic. - Update the comment in the compiler sanitizers feature file to explain why we are trying to enable LTO (Clang sanitizers require it). - Clean up temporary _SAVED variables at the end of function execution in various feature and library tests. - Remove 2 unsubstituted and unused variables from extra.mk.in. - Support the -Wa,--noexecstack flag to the compiler and linker; enable it by default.

5 years ago

ax_subdirs_configure.m4

m4/*.m4: update from upstream [ci skip]

6 years ago

buildsys.m4

autoconf 2.71: using ${as_echo} is deprecated

3 years ago

gettext.m4

m4/*.m4: update from upstream

7 years ago

nls.m4

m4/: tidy up NLS logic We shouldn't do all the NLS checks before parsing --enable-nls; it should be the other way around: only do the checks if --enable-nls=yes was given. Since all but one of our translations are currently broken, also change the default from yes to no. This can be revisited after our translations are brought up to scratch.

6 years ago

po.m4

AC_PROG_MKDIR_P is broken beyond repair; remove it

3 years ago

Configure Feed

Configure Feed