unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: 80 new build failures for MIPS on the 'dbus-update' branch
Date: Thu, 22 Oct 2015 16:43:29 +0200	[thread overview]
Message-ID: <20151022144329.GA9655@debian> (raw)
In-Reply-To: <87vb9zhu64.fsf@member.fsf.org>

On Thu, Oct 22, 2015 at 10:09:07PM +0800, 宋文武 wrote:
> Andreas Enge <andreas@enge.fr> writes:
> > Do you see where this comes in? The git commits in dbus-update do not
> > mention p11-kit, and
> >    $ guix graph gnome-terminal | grep p11
> > returns nothing.

Sorry, I was confused here and did not check with the dbus-update branch.

> oops, It's introduced by:
>   gtk+ -> rest -> libsoup -> glib-networking -> p11-kit
> if we can't fix p11-kit on mips, then rest can be removed from gtk+.
> it's used for “cloud printing”.

This looks like a good temporary fix, to disentangle the dbus-update branch.
My impression is that we should not have changed so much at the same time,
anyway, and instead have concentrated on the dbus-update and closely related
modifications, then merged back, then done other modifications and updates
like gtk+.

> maybe not releated, the build log of p11-kit
> <http://hydra.gnu.org/build/736459/log/raw> have:
>   ffi.h:224:5: warning: "HAVE_LONG_DOUBLE_VARIANT" is not defined
> which is fixed in the newer version (3.2.1) of libffi.

Interesting, so maybe the problem will be solved; then we can still add
rest as an input to gtk+ again.

Thanks!

Andreas

  reply	other threads:[~2015-10-22 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 23:50 80 new build failures for MIPS on the 'dbus-update' branch Mark H Weaver
2015-10-22 12:56 ` Andreas Enge
2015-10-22 14:09   ` 宋文武
2015-10-22 14:43     ` Andreas Enge [this message]
2015-10-23  9:30       ` Andreas Enge
2015-10-23 10:08         ` Andreas Enge
2015-10-24  1:48         ` 宋文武
2015-10-24  7:48           ` Andreas Enge
2015-10-25 21:33       ` Ludovic Courtès

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=20151022144329.GA9655@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.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 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).