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: Sat, 24 Oct 2015 09:48:49 +0200 [thread overview]
Message-ID: <20151024074849.GA3817@debian> (raw)
In-Reply-To: <8737x1yr3j.fsf@member.fsf.org>
On Sat, Oct 24, 2015 at 09:48:00AM +0800, 宋文武 wrote:
> I remove rest from gtk+, build successful locally (x86_64), and pushed.
> Are you fails on mips64el?
No, also on x86_64. I am not sure what happened, maybe I made a mistake
somewhere.
Andreas
next prev parent reply other threads:[~2015-10-24 7:49 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
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 [this message]
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=20151024074849.GA3817@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).