From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: 'gobject-introspection': No such file or directory
Date: Tue, 05 Feb 2013 10:00:04 +0100 [thread overview]
Message-ID: <87ehgvuodn.fsf@gnu.org> (raw)
In-Reply-To: <877gmna8uq.fsf@karetnikov.org> (Nikita Karetnikov's message of "Mon, 04 Feb 2013 19:43:12 -0500")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> The solution is to patch Python to refer to our ‘sh’ instead of /bin/sh
>> (as is done for Guile’s ice-9/popen.scm).
>
>> Can you do that?
>
> I changed 'arguments', but 'gobject-introspection' failed with the same
> error.
>
> python.scm:
>
> (arguments `(#:tests? #f ; XXX: some tests fail
> #:phases (alist-cons-before
> 'configure 'pre-configure
> (lambda* (#:key inputs #:allow-other-keys)
> (let ((bash (assoc-ref inputs "bash")))
> (substitute* "Lib/subprocess.py"
> (("/bin/sh")
> (string-append bash "/bin/bash")))))
> %standard-phases)))
Good. You can already commit that one (but please make it
(string-append bash "/bin/sh") rather.)
> subprocess.py:
>
> if shell:
> args = ["/nix/store/4mg8b8vvmava68y64qmm70gqfnhhjzmx-bash-4.2/bin/bash", "-c"] + args
> if executable:
> args[0] = executable
Are you looking at the subprocess.py that’s actually mentioned in the
gobject-introspection backtrace?
If yes, then it likely means that it’s the caller–i.e., some .py file in
gobject-introspection–that’s passing /bin/sh somewhere. Can you check
the files mentioned in the backtrace?
HTH,
Ludo’.
next prev parent reply other threads:[~2013-02-05 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 14:45 'gobject-introspection': No such file or directory Nikita Karetnikov
2013-01-28 16:46 ` Ludovic Courtès
2013-02-01 18:26 ` Nikita Karetnikov
2013-02-04 22:36 ` Ludovic Courtès
2013-02-05 0:43 ` Nikita Karetnikov
2013-02-05 9:00 ` Ludovic Courtès [this message]
2013-02-07 8:56 ` Nikita Karetnikov
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=87ehgvuodn.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).