From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Packages with libraries and binaries
Date: Sat, 05 Oct 2013 14:52:47 +0200 [thread overview]
Message-ID: <87txgvswv4.fsf@gnu.org> (raw)
In-Reply-To: <20131004175542.GA27833@debian> (Andreas Enge's message of "Fri, 4 Oct 2013 19:55:42 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> On Sun, Sep 22, 2013 at 09:44:18PM +0200, Ludovic Courtès wrote:
>> In such cases, we must set the RUNPATH, using patchelf as Nikita notes.
>> The recommended way to do that is to use ‘augment-rpath’ from (guix
>> build rpath), as done in python.scm (make sure to add ‘patchelf’ as an
>> input).
>
> When copy-pasting the phases argument from python-2 into cdparanoia, the
> build phase fails as follows:
>
> phase `strip' succeeded after 0 seconds
> starting phase `add-lib-to-runpath'
[...]
> ERROR: In procedure memoize-variable-access!:
> ERROR: Unbound variable: cut
>
> As if an import of module srfi-26 were missing somewhere, but both python and
> cdparanoia use the same gnu build system.
Exactly. You need that snippet, as in python.scm:
--8<---------------cut here---------------start------------->8---
#:modules ((guix build gnu-build-system)
(guix build utils)
(guix build rpath)
(srfi srfi-26))
#:imported-modules ((guix build gnu-build-system)
(guix build utils)
(guix build rpath))
--8<---------------cut here---------------end--------------->8---
#:modules tells what modules are to be imported in the lexical
environment of the build program, while #:imported-modules says what
.scm/.go files need to be available in the build chroot (since srfi-26
is part of Guile, it’s listed in the former but not the latter.)
HTH,
Ludo’.
next prev parent reply other threads:[~2013-10-05 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 12:06 Packages with libraries and binaries Andreas Enge
2013-09-22 19:37 ` Nikita Karetnikov
2013-09-22 19:44 ` Ludovic Courtès
2013-10-04 17:55 ` Andreas Enge
2013-10-05 12:52 ` Ludovic Courtès [this message]
2013-10-06 9:50 ` Andreas Enge
2013-10-04 17:58 ` Andreas Enge
2013-10-05 12:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txgvswv4.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 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.