From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Tue, 09 Dec 2014 21:58:30 +0100 [thread overview]
Message-ID: <87fvcor155.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPPTtio_2-PRr7qc-FBvP3xynkVV8bt_rSPkFpczhHafJQ@mail.gmail.com> (Federico Beffa's message of "Tue, 9 Dec 2014 20:30:00 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> I've pushed the two changes and see that it breaks several packages
> depending on gobject-introspection.
> Looking randomly at some of the failures I see that pango and
> gdk-pixbuf fail to build (and many other failures are a consequence of
> one of these two). So I've tried to build pango with
> gobject-introspection 1.42.0 without any change (no patch, no
> native-search-path) and without the patch, but with
> native-search-path. However, it always fails to build.
>
> So, I've updated pango to the latest 1.36.8 and it builds with the new
> and patched gobject-introspection and I see that the gir files of the
> former include the full path of dynamic libraries.
>
> I've then updated pix-buf to the latest and it builds fine, but have 2
> out of 74 test failures.
Oh oh, OK.
> What do you prefer? Revert to gobject-introspection 1.38.0, or got
> down the version dependency hell?
If you think it will require some more time, then it may be less
disturbing to set up a branch for those changes, and revert the
offending commit in master while the branch is being stabilized. WDYT?
We can set up Hydra to build the branch, so we have feedback, if you
want.
Thanks for investigating,
Ludo’.
next prev parent reply other threads:[~2014-12-09 20:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 14:21 gobject-introspection typelibs and shared libraries Federico Beffa
2014-12-07 20:48 ` Ludovic Courtès
2014-12-07 22:11 ` Federico Beffa
2014-12-08 9:22 ` Ludovic Courtès
2014-12-08 12:21 ` Federico Beffa
2014-12-08 14:51 ` Federico Beffa
2014-12-08 20:37 ` Ludovic Courtès
2014-12-09 19:30 ` Federico Beffa
2014-12-09 20:27 ` Federico Beffa
2014-12-10 4:15 ` Mark H Weaver
2014-12-09 20:58 ` Ludovic Courtès [this message]
2014-12-10 4:39 ` Mark H Weaver
2014-12-10 4:54 ` Mark H Weaver
2014-12-10 8:48 ` Ludovic Courtès
2014-12-10 8:57 ` Federico Beffa
2014-12-10 12:56 ` Ludovic Courtès
2014-12-16 19:45 ` Federico Beffa
2014-12-17 7:20 ` Mark H Weaver
2014-12-17 8:57 ` Ludovic Courtès
2015-01-13 17:10 ` Federico Beffa
2015-01-13 20:22 ` Ludovic Courtès
2015-01-13 21:40 ` Federico Beffa
2015-01-14 20:43 ` Ludovic Courtès
2015-01-15 8:27 ` Federico Beffa
2015-01-15 21:42 ` Ludovic Courtès
2015-01-16 17:07 ` Federico Beffa
2015-01-16 20:47 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2015-01-17 9:46 Federico Beffa
2015-01-17 10:15 ` 宋文武
2015-01-17 12:02 ` Andreas Enge
2015-01-18 9:39 ` Federico Beffa
2015-01-18 13:16 ` Andreas Enge
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=87fvcor155.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@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.