Menu
▾
▴
#749 CL_MACH_VM configure check will fail with future compilers
vm_allocate and task_self are not declared, so they are only found (at link time) if compilation succeed due to compiler support for implicit function declarations. Compilers are going to remove such support by default.
AC_DEFUN([CL_MACH_VM],
[
CL_LINK_CHECK([vm_allocate], [cl_cv_func_vm], ,
[vm_allocate(); task_self();],
[AC_DEFINE([HAVE_MACH_VM],,[have vm_allocate() and task_self() functions])])
])
Hi Florian,
I am not involved with the CLISP project, but it seems to me as if the project has switched to GitLab. It seems as if they imported issues from this tracker there at some point in time in the past (see https://gitlab.com/gnu-clisp/clisp/-/issues).
The clisp.org (redirected to https://clisp.sourceforge.io/) and https://www.gnu.org/software/clisp/ sites still direct bug reporters here, to the SourceForge bug tracker.
I do not see much activity here in the SourceForge project, but the GitLab project seems to be active.
Thus, I am unsure how to reach the CLISP project and report issues. Just opening a bug here might not work.
I have sent an email to clisp-list@lists.sourceforge.net to report this (see https://sourceforge.net/p/clisp/mailman/message/37837093/).
HTH,
Erik
Thanks for the hint, moved: https://gitlab.com/gnu-clisp/clisp/-/issues/42
Thanks for the report. Fixed through commit 72ae177d.