From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Collin J. Doering" <collin@rekahsoft.ca>
Cc: 62672@debbugs.gnu.org
Subject: bug#62672: Unexpected interaction between gobject-introspection and grafts
Date: Thu, 06 Apr 2023 21:33:29 +0200 [thread overview]
Message-ID: <87y1n47qly.fsf@jpoiret.xyz> (raw)
In-Reply-To: <877cuqmf8t.fsf@rekahsoft.ca>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Hi Collin,
"Collin J. Doering" <collin@rekahsoft.ca> writes:
> Hi Josselin,
>
> Thanks for your quick reply. It appears that all dynamic libraries referenced by libgtk.so are correctly referenced (and not missing):
> [...]
> You'll noticed linux-vdso.so.1 doesn't reference a file but afaik this is expected as its a virtual library provided by the kernel.
>
>> These errors can also be caused by dependent libraries not being found,
>> or linker errors, etc. I would suggest to run `ldd` on the .so itself
>> (from glibc), and see what the output is.
>
> This doesn't appear to be the case. Did I miss something?
>
> [...]
>
> Yes, but that makes the error all the more confusing; the original error says that it can't find "/gnu/store/91ar3zh59n19rdn00png5r9hxp3k0y13-gtk-4.8.1/lib/libgtk-4.so.1", however this is the ungrafted gtk package, so it SHOULD (afaik) exist throughout the build. Further, when I enter a simulated build environment, the file does indeed exist.
The ENOFILE can happen while loading _any_ dependency of the required
lib, and will be propagated back. Since the file seems to exist in the
development environment as you mentioned, my guess is that some
dependency somewhere seems to be missing somehow. You could try
manually running the `./configure` script or equivalent that's failing,
with LD_DEBUG=libs set in the environment (or even =all), and seeing if
that error still happens/what the error is precisely. If it doesn't
happen, this would be even more suspicious.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-04-06 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 0:04 bug#62672: Unexpected interaction between gobject-introspection and grafts Collin J. Doering via Bug reports for GNU Guix
2023-04-05 8:11 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-05 16:59 ` Collin J. Doering via Bug reports for GNU Guix
2023-04-06 19:33 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-04-05 19:55 ` John Kehayias via Bug reports for GNU Guix
2023-04-05 20:21 ` Collin J. Doering via Bug reports for GNU Guix
2024-04-27 1:32 ` Collin J. Doering via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1n47qly.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=62672@debbugs.gnu.org \
--cc=collin@rekahsoft.ca \
--cc=dev@jpoiret.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).