From: Guillaume Le Vaillant <glv@posteo.net>
To: guix-devel@gnu.org
Subject: Question about sbcl-package->ecl-package
Date: Wed, 16 Oct 2019 11:26:57 +0200 [thread overview]
Message-ID: <871rvdujku.fsf@yamatai> (raw)
Hi,
I'm trying to package a Common Lisp library and I have a strange
problem.
In 'gnu/packages/lisp.scm', there are packages called 'sbcl-chanl' and
'ecl-chanl' whose definitions are:
--8<---------------cut here---------------start------------->8---
(define-public sbcl-chanl
(let ((commit "2362b57550c2c9238cc882d03553aaa1040b7340")
(revision "0"))
(package
(name "sbcl-chanl")
...)))
(define-public ecl-chanl
(let ((base (sbcl-package->ecl-package sbcl-chanl)))
(package
(inherit base)
(arguments
(substitute-keyword-arguments (package-arguments base)
;; Some phases are modified here so that compiling
;; with ECL works.
...)))))
--8<---------------cut here---------------end--------------->8---
Compiling these two packages works fine.
Now, I define the following new packages:
--8<---------------cut here---------------start------------->8---
(define-public sbcl-simple-parallel-tasks
(let ((commit "db460f7a3f7bbfe2d3a2223ed21e162068d04dda")
(revision "0"))
(package
(name "sbcl-simple-parallel-tasks")
...
(inputs
`(("chanl" ,sbcl-chanl)))
...)))
(define-public ecl-simple-parallel-tasks
(sbcl-package->ecl-package sbcl-simple-parallel-tasks))
--8<---------------cut here---------------end--------------->8---
Compiling 'sbcl-simple-parallel-tasks' works fine.
However, when I try to compile 'ecl-simple-parallel-tasks', guix first
tries to build a different derivation of 'ecl-chanl', which fails
because it apparently doesn't have the modified phases declared in the
definition of 'ecl-chanl'.
More precisely:
- If I do 'guix build ecl-chanl', guix builds
'y60p0wn2hwp5jr0hy2qb09yazkp29m7i-ecl-chanl-0.4.1-0.2362b57'
successfully.
- If I do 'guix build ecl-simple-parallel-tasks', guix tries to build
'qqzlyknj5wgrm0f0nm4wwafv3ldvhrgi-ecl-chanl-0.4.1-0.2362b57'
and fails.
When doing 'guix build ecl-simple-parallel-tasks' I was expecting guix
to use the 'ecl-chanl' I had already compiled as input, but instead it
looks as if it tries to build
'(sbcl-package->ecl-package sbcl-chanl)' instead.
Does anyone know why in this case guix tries to compile a different
derivation of 'ecl-chanl' that I didn't define anywhere?
next reply other threads:[~2019-10-16 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 9:26 Guillaume Le Vaillant [this message]
2019-10-16 11:59 ` Question about sbcl-package->ecl-package Pierre Neidhardt
2019-10-16 12:47 ` Efraim Flashner
2019-10-16 14:06 ` Guillaume Le Vaillant
2019-10-17 12:01 ` Guillaume Le Vaillant
2019-10-17 12:20 ` Pierre Neidhardt
2019-10-17 13:09 ` Guillaume Le Vaillant
2019-10-17 13:16 ` Pierre Neidhardt
2019-10-17 13:35 ` Guillaume Le Vaillant
2019-10-17 13:48 ` Pierre Neidhardt
2019-10-17 14:47 ` Guillaume Le Vaillant
2019-10-17 14:54 ` Pierre Neidhardt
2019-10-18 9:22 ` Pierre Neidhardt
2019-10-18 11:55 ` Guillaume Le Vaillant
2019-10-17 13:16 ` 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=871rvdujku.fsf@yamatai \
--to=glv@posteo.net \
--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).