unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "49122@debbugs.gnu.org" <49122@debbugs.gnu.org>
Subject: bug#49122: (No Subject)
Date: Sun, 20 Jun 2021 23:59:38 +0000	[thread overview]
Message-ID: <zUU7RiK8_yvzxLZxIyAIo3cUoO7pKuN4KeRmxwHUN9UYHN9i0TDX0OdXu5-GxRbxgecj3HGwfMF7DEnqS9LF0aKtHcxbSWWJX_9Gn-VFclY=@protonmail.com> (raw)
In-Reply-To: <NU1oXuYXmLmLVwBBnwvv_21WrRNCjHFfDC16NAPAg8uzXlw9N0FhL69CwdG2KdPRBpb5YoOEjDr8ZiDagZpJfLTOFXxOJLecW-HlRjZONMo=@protonmail.com>

I've managed to fix the initial problem I noted, but this would depend on having cairo as an input so that gobject-introspection can find the library to patch the typelib. Unfortunately, this would be a circular dependency. This is a long standing issue with how cairo is handled here (see, e.g., https://gitlab.freedesktop.org/cairo/cairo/-/issues/141).

I don't know how circular dependencies are solved in guix, so I'm not sure what to do to fix this. gobject-introspection doesn't need cairo to build or function, so the build depends is not really needed other than to fix this bug. So this could be done with a separate package or in two steps?




  reply	other threads:[~2021-06-21  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 18:29 bug#49122: gobject-introspection and not finding cairo John Kehayias via Bug reports for GNU Guix
2021-06-20 23:59 ` John Kehayias via Bug reports for GNU Guix [this message]
2024-01-20 22:18   ` Maxim Cournoyer
2021-06-21  2:04 ` bug#49122: (No Subject) John Kehayias via Bug reports for GNU Guix
2021-09-07 23:06 ` bug#49122: gobject-introspection and not finding cairo Raghav Gururajan via Bug reports for GNU Guix
2021-09-08  0:07   ` Raghav Gururajan 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='zUU7RiK8_yvzxLZxIyAIo3cUoO7pKuN4KeRmxwHUN9UYHN9i0TDX0OdXu5-GxRbxgecj3HGwfMF7DEnqS9LF0aKtHcxbSWWJX_9Gn-VFclY=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=49122@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    /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).