unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: GLib: GIO's tests fail
Date: Mon, 07 Jan 2013 22:01:40 +0100	[thread overview]
Message-ID: <87d2xgzozv.fsf@gnu.org> (raw)
In-Reply-To: <87y5g44yp9.fsf@karetnikov.org> (Nikita Karetnikov's message of "Mon, 07 Jan 2013 13:47:30 -0500")

Hi Nikita,

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> I removed '#:phases' from 'arguments' and added '#:configure-flags':
>
>   (arguments `(#:configure-flags '("--disable-modular-tests"
>                                    "--disable-rebuilds")))

I guess this disables parts of the test suite.  That’s OK as a first
stab, but eventually we may want to actually fix the problem.  ;-)

> /bin/sh: line 19: python2.5: command not found
> make[4]: *** [install-codegenPYTHON] Error 127

[...]

> AFAICT, the problem is the lack of 'python' in Guix.

Indeed.

> Here is a corresponding snippet from Nixpkgs:
>
> # * Make it build without python
> #     Problem: an example (test?) program needs it.
> #     Possible solution: disable compilation of this example somehow
> #     Reminder: add 'sed -e 's@python2\.[0-9]@python@' -i
> #       $out/bin/gtester-report' to postInstall if this is solved
>
>   buildNativeInputs = [ perl pkgconfig gettext python ];
>
> Is it possible to solve this without 'python'?

Is there a --disable-python switch or something?  If not, you could
check whether it’s just a tiny little thing that needs to be patched to
avoid the dependency.

Or...  you can add a package for Python.  :-)

Thanks,
Ludo’.

      reply	other threads:[~2013-01-07 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31  1:12 GLib: GIO's tests fail Nikita Karetnikov
2013-01-01 23:11 ` Ludovic Courtès
2013-01-05  3:11   ` Nikita Karetnikov
2013-01-05 15:27     ` Ludovic Courtès
2013-01-07 18:47       ` Nikita Karetnikov
2013-01-07 21:01         ` Ludovic Courtès [this message]

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=87d2xgzozv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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).