From: Cyril Roelandt <tipecaml@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add gobject-introspection.
Date: Sun, 15 Sep 2013 16:45:09 +0200 [thread overview]
Message-ID: <5235C7F5.4070000@gmail.com> (raw)
In-Reply-To: <87d2oeqvnv.fsf@gnu.org>
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.
next prev parent reply other threads:[~2013-09-15 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 23:39 [PATCH] gnu: Add gobject-introspection Cyril Roelandt
2013-09-12 8:41 ` Ludovic Courtès
2013-09-15 14:45 ` Cyril Roelandt [this message]
2013-09-15 21:09 ` Ludovic Courtès
2013-09-15 21:38 ` Ludovic Courtès
2013-09-16 23:34 ` Cyril Roelandt
2013-09-17 8:40 ` Ludovic Courtès
2013-09-29 20:08 ` [PATCH v2] " Cyril Roelandt
2013-09-29 20:26 ` Ludovic Courtès
2013-09-29 21:09 ` Cyril Roelandt
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=5235C7F5.4070000@gmail.com \
--to=tipecaml@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.