From: Guillaume Le Vaillant <glv@posteo.net>
To: Foo Chuan Wei <chuanwei.foo@hotmail.com>
Cc: guix-devel@gnu.org, cox.katherine.e@gmail.com
Subject: Re: cl-gsll fails to load
Date: Fri, 10 Dec 2021 13:41:13 +0000 [thread overview]
Message-ID: <87k0gch8ml.fsf@kitej> (raw)
In-Reply-To: <PU1PR01MB2155B0E7C391C382CEF162088D719@PU1PR01MB2155.apcprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Foo Chuan Wei <chuanwei.foo@hotmail.com> skribis:
> On 2021-12-07 12:27 +0000, Guillaume Le Vaillant wrote:
>> I think the problem comes from the fact that the build system for
>> cl-xxx packages doesn't use the custom phases added to some sbcl-xxx
>> packages (like the 'fix-cffi-paths' phase of sbcl-gsll). Instead a fixed
>> set of phases is used (see '%standard-phases/source' from
>> "guix/build/asdf-build-system.scm", used in the
>> 'sbcl-package->cl-source-package' function from
>> "guix/build-system/asdf.scm").
>
> Are you sure about this? From my observations, the cl-xxx packages do
> use the custom phases added to the sbcl-xxx packages. When I install
> cl-gsll and look into its store directory
> (~/.guix-profile/share/common-lisp/source/cl-gsll/), I do see the
> effect of sbcl-gsll's custom phase ("fix-cffi-paths").
Indeed, it looks like custom phases are taken into considerations now (I
don't remember when this got fixed).
However although cl-cffi has a custom phase to fix the path to gcc, it
still tries to run "gcc" instead of "/gnu/store.../gcc" when compiling
cl-gsll from a REPL. I'll try to find where this bare "gcc" comes from...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-12-10 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 6:16 cl-gsll fails to load Foo Chuan Wei
2021-12-07 12:27 ` Guillaume Le Vaillant
2021-12-10 4:07 ` Foo Chuan Wei
2021-12-10 13:41 ` Guillaume Le Vaillant [this message]
2021-12-10 15:27 ` Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0gch8ml.fsf@kitej \
--to=glv@posteo.net \
--cc=chuanwei.foo@hotmail.com \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).