Packages with libraries and binaries

Packages with libraries and binaries

[Andreas Enge]

When trying to use cdparanoia, I noticed the following:

$ ldd `which cdparanoia`

        linux-vdso.so.1 =>  (0x00007fff1e9dd000)
        libcdda_interface.so.0 => not found
        libcdda_paranoia.so.0 => not found
        libm.so.6 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libm.so.6 (0x00007fb37355b000)
        librt.so.1 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/librt.so.1 (0x00007fb373353000)
        libc.so.6 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libc.so.6 (0x00007fb372fa5000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb372d89000)
        /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fb373877000)

The two missing libraries are part of the package itself; apparently, they
do not get encoded into the rpath. Could this be handled somehow by the build
system? Should it be done in the package definition? Or should I set an
LD_LIBRARY_PATH?

Andreas

Re: Packages with libraries and binaries

[Nikita Karetnikov]

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

> The two missing libraries are part of the package itself; apparently, they
> do not get encoded into the rpath. Could this be handled somehow by the build
> system? Should it be done in the package definition? Or should I set an
> LD_LIBRARY_PATH?

You can adjust RPATH with patchelf.  Here’s an example [1] (ignore the
comment about shared libs).

Does it answer your question?

[1] https://lists.gnu.org/archive/html/guix-devel/2013-07/txt5Qs_mNF2lH.txt

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Packages with libraries and binaries

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> When trying to use cdparanoia, I noticed the following:
>
> $ ldd `which cdparanoia`
>
>         linux-vdso.so.1 =>  (0x00007fff1e9dd000)
>         libcdda_interface.so.0 => not found
>         libcdda_paranoia.so.0 => not found
>         libm.so.6 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libm.so.6 (0x00007fb37355b000)
>         librt.so.1 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/librt.so.1 (0x00007fb373353000)
>         libc.so.6 => /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libc.so.6 (0x00007fb372fa5000)
>         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb372d89000)
>         /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fb373877000)

That’s an indication that cdparanoia doesn’t use Libtool...

> The two missing libraries are part of the package itself; apparently, they
> do not get encoded into the rpath. Could this be handled somehow by the build
> system? Should it be done in the package definition? Or should I set an
> LD_LIBRARY_PATH?

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).

HTH,
Ludo’.

Re: Packages with libraries and binaries

[Andreas Enge]

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'
Backtrace:
In ice-9/boot-9.scm:
 157: 15 [catch #t #<catch-closure 1cb5d20> ...]
In unknown file:
   ?: 14 [apply-smob/1 #<catch-closure 1cb5d20>]
In ice-9/boot-9.scm:
  63: 13 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 12 [eval # #]
In ice-9/boot-9.scm:
2320: 11 [save-module-excursion #<procedure 1ce4bc0 at ice-9/boot-9.scm:3961:3 ()>]
3966: 10 [#<procedure 1ce4bc0 at ice-9/boot-9.scm:3961:3 ()>]
1645: 9 [%start-stack load-stack ...]
1650: 8 [#<procedure 1ceadb0 ()>]
In unknown file:
   ?: 7 [primitive-load "/nix/store/m95ni0aq76l1vrlvdjrz2g4gw13md321-cdparanoia-10.2-guile-builder"]
In ice-9/eval.scm:
 387: 6 [eval # ()]
In /nix/store/5kbwbhzkvndzlx0yldg3532xn7j74cwz-module-import/guix/build/gnu-build-system.scm:
 368: 5 [#<procedure 1ef74c0 at /nix/store/5kbwbhzkvndzlx0yldg3532xn7j74cwz-module-import/guix/build/gnu-build-system.scm:364:9 (expr)> #]
In ice-9/r4rs.scm:
  90: 4 [dynamic-wind #<procedure 221f540 at ice-9/eval.scm:416:20 ()> ...]
In ice-9/eval.scm:
 387: 3 [eval # #]
 386: 2 [eval # #]
 393: 1 [eval # #]
In unknown file:
   ?: 0 [memoize-variable-access! #<memoized cut> #<directory (guile-user) 1ca7c60>]

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.

Andreas

Re: Packages with libraries and binaries

[Ludovic Courtès]

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’.

Re: Packages with libraries and binaries

[Andreas Enge]

On Sat, Oct 05, 2013 at 02:52:47PM +0200, Ludovic Courtès wrote:
> Exactly.  You need that snippet, as in python.scm:

That did it, thanks for the explanations!

Andreas

Re: Packages with libraries and binaries

[Andreas Enge]

And can I use the same code for libraries using other libraries of the same
package, by changing "bin" to "lib" in the code snippet?

For instance, one has
$ ldd /nix/store/bplvsx34rzpn85vly086l0jhmhil9ncg-icu4c-50.1.1/lib/libicuuc.so
...
        libicudata.so.50 => not found
...

where the unfound library resides in the same directory.

Andreas

Re: Packages with libraries and binaries

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> And can I use the same code for libraries using other libraries of the same
> package, by changing "bin" to "lib" in the code snippet?
>
> For instance, one has
> $ ldd /nix/store/bplvsx34rzpn85vly086l0jhmhil9ncg-icu4c-50.1.1/lib/libicuuc.so
> ...
>         libicudata.so.50 => not found
> ...
>
> where the unfound library resides in the same directory.

Yes, in this case the RUNPATH of libicuuc.so needs to be augmented to
contain $out/lib, where libicudata.so lives.

Ludo’.