On 09/12/2013 10:41 AM, Ludovic Courtès wrote:
No. Could you try to grep the source to see what produces this message?
Oh, I thought the message was directly produced by libtool or the
linker, but yes, it's definitely an error message from
gobject-introspection. I investigated this a bit. During the 'build'
phase, the '_resolve_non_libtool' method is called from
giscanner/shlibs.py. It tries to get the path to some libraries (here,
gobject-2.0 and glib-2.0). In order to do this, it runs this command:
$ /nix/store/2awqnfxjrcm2b8s481zwsnfdic3inkdi-bash-4.2/bin/bash \
./libtool --mode=execute ldd \
/tmp/nix-build-gobject-introspection-1.37.6.drv-0/gobject-introspection-1.37.6/tmp-introspectS0TNXv/GLib-2.0
(tmp-instropectS0TNXv is a random directory)
On i686, this works perfectly. On x86-64, I get:
'not a dynamic executable'
If I 'cheat' by replacing 'ldd' by '/usr/bin/ldd', then everything works
as expected.
More info:
$ ldd --version
ldd (GNU libc) 2.17
...
$ /usr/bin/ldd --version
ldd (Debian EGLIBC 2.17-5) 2.17
...
Cyril.
