Looking at rspamd, the Makefile indicates a need for BLAS and CBLAS
but the resulting executables do not reference them.
It turns out absent a specific CONFIGURE_ARGS+= -DENABLE_BLAS=ON
then the build substitutes a simple pair of codes from kann, instead
of using BLAS. (The needed codes are saxpy and sgemm.)
Is it time to remove the blas references from rspamd?
J
Index: Makefile
===================================================================
RCS file: /cvs/ports/mail/rspamd/Makefile,v
retrieving revision 1.118
diff -u -p -r1.118 Makefile
--- Makefile 11 Oct 2023 13:28:54 -0000 1.118
+++ Makefile 27 Oct 2023 16:46:05 -0000
@@ -14,7 +14,7 @@ MAINTAINER= Stuart Henderson <stu.ports@
PERMIT_PACKAGE= Yes
WANTLIB += ${COMPILER_LIBCXX}
-WANTLIB += blas c crypto glib-2.0 fmt icudata icui18n icuio icuuc
+WANTLIB += c crypto glib-2.0 fmt icudata icui18n icuio icuuc
WANTLIB += intl m pcre2-8 sodium sqlite3 ssl util z zstd
# XXX switch to vectorscan for wider arch support?
@@ -50,11 +50,6 @@ LIB_DEPENDS= archivers/zstd \
security/libsodium \
textproc/icu4c
RUN_DEPENDS= databases/redis
-
-# uses cblas headers; pull this in via LDEP and register an "extra"
dependency
-# on cblas lib to make sure rspamd gets updated for major changes in
cblas
-LIB_DEPENDS+= math/cblas
-WANTLIB+= cblas
BUILD_DEPENDS+= devel/ragel
# /var/rspamd needs to exist for tests to run
