From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Python-build-system does not honour phases
Date: Tue, 10 Sep 2013 19:48:30 +0200 [thread overview]
Message-ID: <87txhsbma9.fsf@gnu.org> (raw)
In-Reply-To: <20130910082655.GA8621@debian> (Andreas Enge's message of "Tue, 10 Sep 2013 10:26:55 +0200")
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Andreas Enge <andreas@enge.fr> skribis:
> On Mon, Sep 09, 2013 at 11:35:55PM +0200, Ludovic Courtès wrote:
>> The problem is that both the gnu-build-system and the
>> python-build-system were getting imported, and both export a
>> ‘%standard-phases’.
>
> That is what I thought. I tried to add a
> #:use-module ((guix build-system gnu)
> #:select (gnu-build-system))
> but that was not enough.
You’re mixing different things: the line above is on the host side,
whereas the patch I proposed changes the modules imported on the build
side.
>> The fix is to use only python-build-system:
>
> That also does not seem to work.
Could you be more specific? :-)
With the patch I sent, the builder should start with:
(begin
(use-modules (guix build python-build-system)
(guix build utils))
...)
So the global variable named ‘%standard-phases’ here is necessarily that
of (guix build python-build-system).
Can you try this patch to check the value of ‘phases’?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 595 bytes --]
diff --git a/guix/build/python-build-system.scm b/guix/build/python-build-system.scm
index 8429979..1b5eaa8 100644
--- a/guix/build/python-build-system.scm
+++ b/guix/build/python-build-system.scm
@@ -96,6 +96,6 @@
(define* (python-build #:key inputs (phases %standard-phases)
#:allow-other-keys #:rest args)
"Build the given Python package, applying all of PHASES in order."
- (apply gnu:gnu-build #:inputs inputs #:phases phases args))
+ (apply gnu:gnu-build #:inputs inputs #:phases (pk 'the-python-phases phases) args))
;;; python-build-system.scm ends here
[-- Attachment #3: Type: text/plain, Size: 167 bytes --]
[...]
> Maybe we should try to use a variable name %python-standard-phases instead.
That would be cheating. ;-)
And really, it’s unnecessary.
Ludo’.
next prev parent reply other threads:[~2013-09-10 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 22:26 Python-build-system does not honour phases Andreas Enge
2013-09-09 21:35 ` Ludovic Courtès
2013-09-10 8:26 ` Andreas Enge
2013-09-10 13:28 ` Andreas Enge
2013-09-10 17:53 ` Ludovic Courtès
2013-09-10 19:07 ` Andreas Enge
2013-09-10 19:27 ` Andreas Enge
2013-09-10 21:20 ` Ludovic Courtès
2013-09-10 21:34 ` Andreas Enge
2013-09-11 13:55 ` Andreas Enge
2013-09-11 17:45 ` Ludovic Courtès
2013-09-10 17:48 ` Ludovic Courtès [this message]
2013-09-10 18:31 ` Andreas Enge
2013-09-10 21:18 ` Ludovic Courtès
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=87txhsbma9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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).