| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sam James <sam@gentoo.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clang 16 makes -Wimplicit-function-declaration an error by default.
Signed-off-by: Sam James <sam@gentoo.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clang 16 makes -Wimplicit-function-declaration an error by default.
Signed-off-by: Sam James <sam@gentoo.org>
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Clang 16 makes -Wimplicit-function-declaration an error by default.
Signed-off-by: Sam James <sam@gentoo.org>
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| | |
* m4/ax_r_package.m4 (AX_R_PACKAGE): Use packageDescription instead of
the inappropriate system.file.
|
| |
| |
| |
| |
| | |
* m4/ax_r_package.m4 (AX_R_PACKAGE): Use compareVersion instead of
comparing strings.
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
boost_base: add /opt/homebrew to search paths
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Users with Boost installed via homebrew on arm64 (M1) hardware will
have the libs under this path. Not sure if this is something you'd want
to accomodate, but we currently patch this into the macro, so have
decided to upstream.
|
| | | | |
|
|/ / / |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
Add a few python version 3.12 3.11 3.10
Signed-off-by: Bastien Roucariès <rouca@debian.org>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Debian adds a custom sysconfig scheme to system python installs,
"posix_local". This is the default scheme, and it redirects local
users' Python module installs to /usr/local even though Python is
installed with a /usr prefix. Both are on Debian's python's sys.path
module search path.
Autoconf and its users understand prefixes, and are likely to select
/usr/local, explicitly. Select the "posix_prefix" scheme, with the
user-supplied prefix.
Previously this custom sysconfig scheme was specified in
distutils.sysconfig, but not sysconfig itself. As distutils is being
deprecated, the custom scheme is now specified in sysconfig, since
Debian's Python 3.10 (3.10.2-4).
|
|\ \
| | |
| | | |
ax_boost_json: implement for Boost::JSON library
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add AX_BOOST_JSON() to search for Boost::JSON
(which is in boost 1.75 or newer)
Macro derived from AX_BOOST_RANDOM().
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
apophenia fails to cross build from source, because it fails to locate
the mysql client libraries. It does so via the AX_LIB_MYSQL macro, which
consults mysql_config, which cannot work during cross builds. This patch
extends the AX_LIB_MYSQL
macro to try pkg-config before mysql_config.
Signed-off-by: Bastien Roucariès <rouca@debian.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
projectm fails to cross build from source, because it uses AX_HAVE_QT
from autoconf-archive and that macro hard codes the build architecture
qmake. We use the
host architecture for qmake.
Signed-off-by: Bastien Roucariès <rouca@debian.org>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
telegram-cli fails to cross build from source, because it uses
AX_LUA_HEADERS, which happens to use AC_RUN_IFELSE to compute the lua
version. As it turns out, the version is also available as an integer,
which allows using the cross-friendly AC_COMPUTE_INT. The attached patch
updates AX_LUA_HEADERS to use AC_COMPUTE_INT.
Signed-off-by: Bastien Roucariès <rouca@debian.org>
debian-bug: https://bugs.debian.org/956713
|
|\ \
| | |
| | | |
ax_cxx_compile_stdcxx: Fix for MSVC
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MSVC always sets __cplusplus to 199711L in older versions; newer versions
do the same unless /Zc:__cplusplus is specified as well as a /std:c++<NN>
switch:
https://devblogs.microsoft.com/cppblog/msvc-now-correctly-reports-__cplusplus/
This fixes a regression compared to the old separate
AX_CXX_COMPILE_STDCXX_11, etc macros which didn't check the value of
__cplusplus so worked OK with MSVC.
|
|\ \ \
| | | |
| | | | |
Remove duplicate $PYTHON_EXTRA_LIBS variable
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
nf-config may not be installed under the same directory as nc-config.
To avoid the automatic definition of nf-config, setting of NF_CONFIG
variable is introduced for a workaround.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The ac_cv_c_compiler_gnu wasn't properly restored to original
state (f.e. yes), but value of the "save" variable was used:
ac_cv_c_compiler_gnu=${ac_cv_c_compiler_gnu=saved_ac_cv_c_compiler_gnu}
Additionally, we don't need to cache the saved_ac_cv_c_compiler_gnu
and was_set_ac_cv_c_compiler_gnu, so remove the ac_cv_ from their names.
This would not manifest on a single run, but any repeated run with cache
file (./configure -C) would be broken.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix deprecated things in ax_prototype.m4
|
| |/ /
| | |
| | | |
Fix deprecated things in ax_prototype.m4, other small changes.
|
|\ \ \
| | | |
| | | | |
Fix Python version-string comparisons in ax_devel_python.m4
|
| |/ /
| | |
| | |
| | | |
comparisons evaluate correctly between < .10 and >= .10 micro version numbers
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
AX_CC_FOR_BUILD: deprecate in favor of AX_PROG_CC_FOR_BUILD
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The AX_PROG_CC_FOR_BUILD has seen a lot more updates than
AX_CC_FOR_BUILD, and is generally way more complete. The latter
hardcoded `gcc` as the native compiler fallback and lacks any of
the standard $build- prefix searches.
It also uses non-standard cache vars -- it's using the bfd_cv_xxx
namespace instead of the ax_cv_xxx namespace everything else does.
Otherwise, the macros largely have the same intention: to find a
compiler for the build system, and setup the exe extension. So
deprecate AX_CC_FOR_BUILD and have it redirect automatically.
|
|\ \ \
| | | |
| | | | |
AX_CXX_COMPILE_STDCXX: add C++20 support
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
detect qtmake-qt5, moc-qt5 etc in ax_have_qt.m4
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
AX_VALGRIND_CHECK: Fix "nothing to be done".
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Recursive targets associated with AM_EXTRA_RECURSIVE_TARGETS() macro
calls should end with "-local", not "-am". Correct the
check-valgrind{-vgtool}-am rules accordingly. This addresses a
problem where the calling "make check-valgrind" resulted in "nothing
to be done".
See the Automake manual Section "Recursing subdirectories" for
details:
https://www.gnu.org/software/automake/manual/automake.html#Subdirectories
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Move the AM_EXTRA_RECURSIVE_TARGETS() macro calls inside of the
AX_VALGRIND_CHECK definition to force the AM_EXTRA_RECURSIVE_TARGETS()
macro calls to be processed as part of AX_VALGRIND_CHECK. The
recursive targets were otherwise not generated by Automake when using
an installed copy of the `ax_valgrind_check.m4' file
(e.g. `/usr/share/aclocal/ax_valgrind_check.m4').
|