That is because these files were compiled with a build of SBCL that has SB-threads in it. Apparently, fasls compiled with a threaded SBCL are not compatible with fasls compiled without threads, so we added an "-s". This was done by analogy with the Allegro fasls, which are "s" for "SMP." Probably "-sbt" or something more informative would have been a better choice.
Cheers, R
On 6 Oct 2024, at 19:54, Greg Bennett wrote:
Hi from Greg Bennett who is running 3.3.7 as part of sbcl-2.4.8-linux-x64 under linux mint.
I must begin by thanking Robert G for all his efforts on maintaining asdf !!
In ~/.config/common-lisp/source-registry.conf.d there is the file gb-source.conf
The live element of that file is (:tree "/home/gwbennett/RESERVE/mintq/")
When compiling a collection of systems I see results like this:
; compiling file "/home/gwbennett/RESERVE/mintq/source/window-basics/menus/menu-sblx.lsp" (written 13 MAY 2024 05:45:54 PM):
; wrote /home/gwbennett/.cache/common-lisp/sbcl-2.4.8-linux-x64-s/home/gwbennett/RESERVE/mintq/source/window-basics/menus/menu-sblx-tmpQXR7SNXD.fasl ; compilation finished in 0:00:00.024
I wonder why the fasls are written to ...../sbcl-2.4.8-linux-x64-s/home.... rather than the path without the -s ? ^^
My ~/.config/common-lisp/asdf-output-translations.conf.d is empty.
The fasls are all there in the -s directory tree and, I assume, are the files which are loaded through the load phase of (asdf:load-system "window-basics)
Hints, pointers, advice all appreciated
Cheers
Greg
Robert P. Goldman Research Fellow Smart Information Flow Technologies (d/b/a SIFT, LLC)
319 N. First Ave., Suite 400 Minneapolis, MN 55401
Voice: (612) 326-3934 Email: rpgoldman@SIFT.net