From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist. Date: Mon, 27 Aug 2018 09:42:27 +0200 Message-ID: <871sakp864.fsf@ambrevar.xyz> References: <87y3cxnj9b.fsf@gmail.com> <87k1ofncss.fsf@gnu.org> <20180827032429.064d878b@uwaterloo.ca> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40392) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuCJf-0005zV-Ek for guix-devel@gnu.org; Mon, 27 Aug 2018 03:52:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fuCAS-000209-Ac for guix-devel@gnu.org; Mon, 27 Aug 2018 03:42:35 -0400 In-reply-to: <20180827032429.064d878b@uwaterloo.ca> 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: Andy Patterson Cc: guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hey Andy! Great to hear for you, it's a big relief to have someone around who is knowledgeable on Common Lisp as I'm starting to feel a bit overwhelmed! :p > As for the initial error - it looks like it's because swank's system > definition file only compiles swank-loader, which I guess is because it > wants to use that loader to load the rest of the system. As a result > the swank-backend package never gets added to the built swank package. Absolutely, I had come to that conclusion as well. There is also another upstream pull request that attempts to fix the same problem, from a different angle: https://github.com/slime/slime/pull/83 I haven't tried it yet. 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--syst= em.fasl file. This file is then referenced in /gnu/store=E2=80=A6-PACKAGE/lib/PACK= AGE.asd. So when a Common Lisp package looks for its dependencies, it searches for a PACKAGE.asd file in the LIBRARY_PATH environment variable. Is this correct? If so, what would be the steps to package a Common Lisp library without ASD= F? Is it possible to create a bundle without ASDF? How are multiple .fasl fil= es loaded when put in a folder pointed by LIBRARY_PATH? Do we absolutely need= a .asd file? I have skimmed over the ASDF documentation but I am not sure I can find ans= wers there. > 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. 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 par= ts of the backtrace. Let me know. 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 sy= stem (more of a quick & dirty workaround). Cheers! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAluDq2MACgkQm9z0l6S7 zH8wXQgAoE43KIGbbRb5OY5mgRgqsmby2M6bf1oBm9wDkBtLDRXoRS0xqBww4r3l wpCoszctlAgwGZwW5/vu8Q03zvskFMpgv+yvG9LwyF2alrf2fU/yx1AhDxCO8dU6 2Stxl7lGQz/tosjN3rCAvP7q5X1p6QGfrGQ47xTYwsVrr/sPNkVyUmBHn0IF8ktx 5TpObAke0pUHH6VwROaHpG4XiEqiXZjbAg6K+Z8kKzi3fO6OpkXhcFWDrvKb4dZ/ oCSmXMkLH2FaYoo6TbErohQ7r5qFuyF5TltS4b8ezdM3qWQJxIqu4J9VUCH/hfJB b1JC18NNiwKXDx2JjKpgqAFYNMH3gw== =e8E3 -----END PGP SIGNATURE----- --=-=-=--