asdf-devel

Download

asdf-devel@common-lisp.net

May 2025

4 participants
2 discussions

Balancing ASDF Configuration for Precompiled OS and User-Compiled FASL Files
by Joseph Mingrone 01 Dec '25

01 Dec '25

Hello, I'm attempting to adjust the ASDF configuration for FreeBSD CL ports/packages to balance the use of precompiled FASL files from OS packages with the ability to compile and write code under users' home directories. Details are below. Any advice would be appreciated. The system-wide configuration [0] I'm attempting to adjust is used both when building FreeBSD CL OS packages and on target systems. Specifically, it: - sets up a central registry, - enforces a filesystem layout, - and configures output translations. With this configuration, users can run `pkg install cl-alexandria-sbcl` and two packages will be installed: - cl-alexandria, essentially the upstream repository, - cl-alexandria-sbcl, the compiled code. From their Lisp implementation, users only need to execute (asdf:load-system :alexandria) and no local compilation is required. However, if a user installs only cl-alexandria without cl-alexandria-sbcl, issues arise. Due to the output translations, ASDF attempts to write compiled code to a location where the user lacks write access. On the other hand, if we remove the output translations on target systems, all FASL files provided by the OS packages are ignored, and ASDF tries to recompile and write them under ~/.cache/common-lisp/. Is there a way to configure ASDF to recognize and accept the FASL files from the OS packages and compile and write any missing FASL files to the default untranslated location under ~/.cache/common-lisp/? Thank you, Joe [0] https://cgit.freebsd.org/ports/tree/devel/cl-asdf/bsd.cl-asdf.mk

3 8

How to run asdf test but ignore full warnings?
by Raymond Toy 07 May '25

07 May '25

GCL 2.7.1 was just recently released and I decided to see if asdf could be compiled with this version. I had to make a small change in uiop/os.lisp to use `system::chdir`, the internal symbol instead of the external symbol. (Not sure if that's really correct, but it does work from the repl.) This seems to allow asdf.lisp to be compiled. The next step was running `make l=gcl GCL=<path>/gcl-2.7.1/bin/gcl test`. However this fails with the message: > Testsuite failed: ASDF compiled with unexpected full warnings There are a few warnings from the compiler. However, I'd like to see how far I can get without fixing the compiler warnings. Is that possible? I just don't want to spend a lot of time fixing compiler warnings if there are more serious issues that are exposed by the testsuite.

4 6