From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] gnu: Add Grue Hunter.
Date: Mon, 03 Jun 2013 12:14:33 +0200 [thread overview]
Message-ID: <87txlffqly.fsf@gnu.org> (raw)
In-Reply-To: <87bo7nubji.fsf@karetnikov.org> (Nikita Karetnikov's message of "Mon, 03 Jun 2013 07:18:41 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> > 2. I'd like to use
>> >
>> > (patch-shebang (string-append bin "/grue-hunter")
>> > (list perl))
>
>> Should be (list (string-append perl "/bin")).
>
> I don't think so. Here's the output of (display (string-append "PERL: " perl "\n")):
>
> PERL: /nix/store/rp1fdpa8fa4cdx3j76yyhi45lgx796nw-perl-5.16.1/bin/perl
>
> And 'perl' is defined like this:
>
> (perl (string-append (assoc-ref %build-inputs
> "perl")
> "/bin/perl"))
Ah OK. Then remove the /perl part ($PATH should only contain directory
names.)
> There is also a corresponding line in 'inputs'. Why does the mentioned
> 'patch-shebang' line return the following?
>
> patch-shebang: /nix/store/k6w3d29k2i9acj3v9ypy19v4sqxki8gk-grue-hunter-1.0/bin/grue-hunter: warning: no binary for interpreter `perl' found in $PATH
Because ‘perl’ was not found in $PATH, because of the above.
HTH,
Ludo’.
prev parent reply other threads:[~2013-06-03 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 19:36 Grue Hunter: Can't create directories in the store Nikita Karetnikov
2013-05-15 0:59 ` Cyril Roelandt
2013-05-15 12:11 ` Ludovic Courtès
2013-05-16 2:35 ` Nikita Karetnikov
2013-05-16 16:33 ` Ludovic Courtès
2013-05-24 9:24 ` Nikita Karetnikov
2013-05-24 12:51 ` Ludovic Courtès
2013-05-24 14:34 ` Nikita Karetnikov
2013-05-24 15:32 ` Ludovic Courtès
2013-05-30 3:40 ` [PATCH] gnu: Add Grue Hunter Nikita Karetnikov
2013-05-30 11:53 ` Ludovic Courtès
2013-06-03 3:18 ` Nikita Karetnikov
2013-06-03 10:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txlffqly.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.