unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 09 Sep 2013 23:35:55 +0200	[thread overview]
Message-ID: <87hadtfzk4.fsf@gnu.org> (raw)
In-Reply-To: <20130907222607.GA28990@debian> (Andreas Enge's message of "Sun, 8 Sep 2013 00:26:07 +0200")

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

Andreas Enge <andreas@enge.fr> skribis:

> Apparently, the #:phases parameter has no influence on the python build
> system.
>
> For instance, when adding
> (arguments
>   `(#:phases '()))
> the package still gets built with the %standard-phases.
>
> I added a line
>    #:phases ,phases
> to
>    (define builder
> at line 131 of guix/build-system/python.scm.
>
> Now I can empty out the phases.

Yes, that’s the correct fix.

> But when I write something like
> #:phases
>   (alist-replace
>    'install
>    ...
>    %standard-phases)
> apparently the %standard-phases from the GNU build system are used,
> as there is an error message that ./configure is not found.
>
> Could maybe someone have a look and propose a solution?

The problem is that both the gnu-build-system and the
python-build-system were getting imported, and both export a
‘%standard-phases’.

The fix is to use only python-build-system:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 644 bytes --]

diff --git a/guix/build-system/python.scm b/guix/build-system/python.scm
index b60adb1..ff34451 100644
--- a/guix/build-system/python.scm
+++ b/guix/build-system/python.scm
@@ -58,7 +58,6 @@
                                            (guix build gnu-build-system)
                                            (guix build utils)))
                        (modules '((guix build python-build-system)
-                                  (guix build gnu-build-system)
                                   (guix build utils))))
   "Build SOURCE using PYTHON, and with INPUTS.  This assumes that SOURCE
 provides a 'setup.py' file as its build system."

[-- Attachment #3: Type: text/plain, Size: 57 bytes --]


Could you check that and commit?

Thanks,
Ludo’.

  reply	other threads:[~2013-09-09 21:41 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 [this message]
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
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=87hadtfzk4.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).