From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Patterson Subject: Re: [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist. Date: Tue, 28 Aug 2018 03:36:35 -0400 Message-ID: <20180828033635.6c07c762@uwaterloo.ca> References: <87y3cxnj9b.fsf@gmail.com> <87k1ofncss.fsf@gnu.org> <20180827032429.064d878b@uwaterloo.ca> <871sakp864.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46300) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuYYe-0002Fd-9q for guix-devel@gnu.org; Tue, 28 Aug 2018 03:37:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fuYYa-00035n-1y for guix-devel@gnu.org; Tue, 28 Aug 2018 03:37:00 -0400 In-Reply-To: <871sakp864.fsf@ambrevar.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: guix-devel Hi Pierre, On Mon, 27 Aug 2018 09:42:27 +0200 Pierre Neidhardt wrote: [...] > One thing I'd like to understand about Common Lisp packages in Guix, > if you can shed some light on this: the build system uses ASDF to > "bundle compile" the entire package into a > single /gnu/store/=E2=80=A6-PACKAGE/lib/PACKAGE--system.fasl file. This = file > is then referenced in /gnu/store=E2=80=A6-PACKAGE/lib/PACKAGE.asd. So whe= n a > Common Lisp package looks for its dependencies, it searches for a > PACKAGE.asd file in the LIBRARY_PATH environment variable. Is this > correct? It's actually using XDG_DATA_DIRS. In Guix, we set up our lisp implementations to check for share/{lisp}-bundle-systems for system definitions. The links there are followed to the lib directory which is a bit arbitrary, but was already being used for built-in libraries by sbcl. >=20 > If so, what would be the steps to package a Common Lisp library > without ASDF?=20 I guess you'd have to basically do what asdf does - call the compiler on the source files with all the right ceremony. > Is it possible to create a bundle without ASDF? I'm guessing it is but it's probably implementation specific. > How > are multiple .fasl files loaded when put in a folder pointed by > LIBRARY_PATH? Do we absolutely need a .asd file? > It could be done with output translations but it's super brittle in my experience. I think some asd file is required regardless. > I have skimmed over the ASDF documentation but I am not sure I can > find answers there. >=20 > > The log listed in the report when using that PR doesn't show the > > full details - but I've just found out that some warnings are being > > treated as errors by sbcl. =20 >=20 > Which log? If it's one of mine, I can post the full backtrace. As > I'm not too familiar (yet) with Common Lisp and SBCL, I might have > missed important parts of the backtrace. Let me know. I was referring to the log you posted at [1]. I'm guessing that there's a warning somewhere just up above. >=20 > Regarding your additions: Have a look at my wip-next-browser branch, > in case it's overlapping with your work. I've borrowed one or two of > the packages you had sent earlier on this list. I've also "fixed" > one thing in the build system (more of a quick & dirty workaround). Sure thing. >=20 > Cheers! >=20 -- Andy [1]