From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: next browser (was: Packaging a free Firefox) Date: Sat, 19 May 2018 21:26:32 +0200 Message-ID: <87efi7wion.fsf@gmail.com> References: <87y3h1g42q.fsf@lassieur.org> <87wowlg3vu.fsf@lassieur.org> <20180503050020.ljaqgrop6uwy24op@abyayala> <87muxhfhqq.fsf@gmail.com> <876044lsci.fsf@gmail.com> <20180503233604.69fd089c@uwaterloo.ca> <87mux8n5gq.fsf@gmail.com> <20180510020041.1e8b3956@uwaterloo.ca> <87d0y3hije.fsf@gmail.com> <3e43616290027f58207fe54d748183e9.squirrel@mailservices.uwaterloo.ca> <877eobh92c.fsf@gmail.com> <20180511010037.6951035e@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]:47349) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fK7Uy-0003zY-HR for guix-devel@gnu.org; Sat, 19 May 2018 15:26:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fK7Ux-0000yr-Fv for guix-devel@gnu.org; Sat, 19 May 2018 15:26:36 -0400 Received: from mail-wm0-x241.google.com ([2a00:1450:400c:c09::241]:54289) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fK7Ux-0000yd-90 for guix-devel@gnu.org; Sat, 19 May 2018 15:26:35 -0400 Received: by mail-wm0-x241.google.com with SMTP id f6-v6so19144119wmc.4 for ; Sat, 19 May 2018 12:26:35 -0700 (PDT) In-reply-to: <20180511010037.6951035e@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@gnu.org --=-=-= Content-Type: text/plain Hooray, I've managed to run Next Browser on GuixSD! The main issue is with cffi: it does not find the libraries installed by Guix. Andy's CFFI package does not seem to cut it. I've asked on the CFFI mailing list and received the following suggestion: https://mailman.common-lisp.net/pipermail/cffi-devel/2018-May/003051.html Now to the question of packaging CFFI for Guix: which road shall we follow? - Package CFFI as-is and tweak `cffi:*foreign-library-directories*` when packaging packages that depend on it. - Package a patched version of CFFI to lookup a specific library folder... But I'm not sure which one. The problem with the first solution is that I'm not sure we can apply it with the way ASDF works with common lisp system like Next. Here follow Next's Makefile: --8<---------------cut here---------------start------------->8--- LISP?=sbcl build-gtk: $(LISP) \ --load next.asd \ --eval '(ql:quickload :next/gtk)' \ --eval '(asdf:make :next/gtk)' \ --eval '(quit)' --8<---------------cut here---------------end--------------->8--- We could patch it to --8<---------------cut here---------------start------------->8--- LISP?=sbcl build-gtk: $(LISP) \ --eval '(ql:quickload :cffi)' \ --eval '(push (format nil "~a/.guix-profile/lib/" (uiop:getenv "HOME")) cffi:*foreign-library-directories*)' \ ## Rest is as usual. --load next.asd \ --eval '(ql:quickload :next/gtk)' \ --eval '(asdf:make :next/gtk)' \ --eval '(quit)' --8<---------------cut here---------------end--------------->8--- Or maybe just set `LISP=sbcl --eval '(ql:quickload :cffi...)`. Suggestions? -- Pierre Neidhardt --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlsAemgACgkQm9z0l6S7 zH8dlQf9Ek7RVF4XMnIkz0j9cii2bw0g7GqbLSF+4QoySqPBQR5kVIkvQYmoviEm v7Bi2dWldFgU1O0m2fcj+0wWyTj3TUIBOPJwx2JAhKT64BxRu6HNIv+zpDgaOp8l SfSg9bWHEpLRbQnFbd3eOMmqmjFnmRcCpwul6rupRtVEWLCwa9nqGHwL/XgkyL0q Ydc4K/QfNsH4vFbu2HuBe+aR4kIibmGmMIj6wLDDvFC61BdnXd+aDZdRncfufuRb YDXzZTAg132iyUJqTTriKJXOJlMGf/SIeB863Dp42ZmRs5qH7+4a8exVOBfh7UBi rmaqLWp4+wHAE6KuteynQgvkkEomxg== =Cb7I -----END PGP SIGNATURE----- --=-=-=--