Change Details

This update also fixes the problem that SBCL would disable the port ASDF in favor of its older, bundled ASDF. SBCL did this because the port was not installing version.lisp-expr. This is still a work-in-progress. A problem that still needs to be addressed is that this newer ASDF wants to auto-generate fasl files under ${LOCALBASE}/lib/common-lisp/asdf/build/ after it is installed. A solution is to create a devel/cl-asdf-sbcl port, like our other CL ports. However, this newer ASDF is also writing under ${LOCALBASE}/lib/common-lisp/asdf/build/ when building the fasl package. I hope to tackle this problem in the next few days, but put this here in case anyone has suggestions. A suggestion from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243176, if I understand correctly, is to eliminate the *-sbcl ports and presumably eliminate (or heavily modify) ${PORTSDIR}/devel/cl-asdf/bsd.cl-asdf.mk and ${PORTDIR}/devel/cl-asdf/files/asdf-init.lisp and allow SBCL to write the fasl files under the user's home directory. PR: 243176 Sponsored by: The FreeBSD Foundation

Also: - resolve warnings from SBCL about the ASDF port being outdated and subsequently disabled [0] by installing version.lisp-expr - re-add the devel/cl-asdf-sbcl port to the tree in a subsequent commit because it is required to avoid filesystem violation errors when building *-sbcl ports with Poudriere. [0] WARNING: You are using ASDF version 3.3.1 (probably from (require "asdf") or loaded by quicklisp) and have an older version of ASDF (and older than 2.27 at that) registered at #P"/usr/local/lib/common-lisp/asdf/asdf.asd". Having an ASDF installed and registered is the normal way of configuring ASDF to upgrade itself, and having an old version registered is a configuration error. ASDF will ignore this configured system rather than downgrade itself. In the future, you may want to either: (a) upgrade this configured ASDF to a newer version, (b) install a newer ASDF and register it in front of the former in your configuration, or (c) uninstall or unregister this and any other old version of ASDF from your configuration. Note that the older ASDF might be registered implicitly through configuration inherited from your system installation, in which case you might have to specify :ignore-inherited-configuration in your in your ~/.config/common-lisp/source-registry.conf or other source-registry configuration file, environment variable or lisp parameter. Indeed, a likely offender is an obsolete version of the cl-asdf debian or ubuntu package, that you might want to upgrade (if a recent enough version is available) or else remove altogether (since most implementations ship with a recent asdf); if you lack the system administration rights to upgrade or remove this package, then you might indeed want to either install and register a more recent version, or use :ignore-inherited-configuration to avoid registering the old one. Please consult ASDF documentation and/or experts.

This update also fixes the problem that SBCL would disable the port ASDFAlso: in favor of its older, bundled ASDF. - resolve warnings from SBCL did this because the port was notabout the ASDF port being outdated and subsequently disabled [0] by installing version.lisp-expr - re-add the devel/cl-asdf-sbcl port to the tree in a subsequent commit because it is required to avoid filesystem violation errors when building *-sbcl ports with Poudriere. This is still a work-in-progress. A problem that still needs to be addressed is[0] that this newer ASDF wants to auto-generate fasl files underWARNING: ${LOCALBASE}/lib/common-lisp/asdf/build/ after it is installed. A solution isYou are using ASDF version 3.3.1 (probably from (require "asdf") or to create a devel/cl-asdf-sbcl port, like our other CL ports. However, thisloaded by quicklisp) and have an older version of ASDF (and older newer ASDF is also writing under ${LOCALBASE}/lib/common-lisp/asdf/build/ whenthan 2.27 at that) registered at building the fasl package. I hope to tackle this problem in the next few days,#P"/usr/local/lib/common-lisp/asdf/asdf.asd". Having an ASDF but put this here in case anyone has suggestions. A suggestion from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243176, if Iinstalled and registered is the normal way of configuring ASDF to understand correctlyupgrade itself, is to eliminate the *-sbcl ports and presumably eliminateand having an old version registered is a (or heavily modify) ${PORTSDIR}/devel/cl-asdf/bsd.cl-asdf.mk andconfiguration error. ASDF will ignore this configured system rather ${PORTDIR}/devel/cl-asdf/files/asdf-init.lisp and allow SBCLthan downgrade itself. In the future, you may want to write the fasleither: (a) files under the user's home directory. PR: 243176upgrade this configured ASDF to a newer version, (b) install a newer Sponsored by: The FreeBSD FoundationASDF and register it in front of the former in your configuration, or (c) uninstall or unregister this and any other old version of ASDF from your configuration. Note that the older ASDF might be registered implicitly through configuration inherited from your system installation, in which case you might have to specify :ignore-inherited-configuration in your in your ~/.config/common-lisp/source-registry.conf or other source-registry configuration file, environment variable or lisp parameter. Indeed, a likely offender is an obsolete version of the cl-asdf debian or ubuntu package, that you might want to upgrade (if a recent enough version is available) or else remove altogether (since most implementations ship with a recent asdf); if you lack the system administration rights to upgrade or remove this package, then you might indeed want to either install and register a more recent version, or use :ignore-inherited-configuration to avoid registering the old one. Please consult ASDF documentation and/or experts.