From: Mark H Weaver <mhw@netris.org>
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/4] gnu: Add xfig.
Date: Tue, 14 Oct 2014 17:58:40 -0400 [thread overview]
Message-ID: <87lhoi71pr.fsf@yeeloong.lan> (raw)
In-Reply-To: <87h9z8uhgc.fsf@gmail.com> (Eric Bavier's message of "Mon, 13 Oct 2014 10:17:55 -0500")
Eric Bavier <ericbavier@gmail.com> writes:
> Btw, I did push a change to xfig and transfig that should let them build
> for i686 (which I tested locally now) and mips (which I don't have the
> means to check locally).
This fixed the issue, and xfig now builds on all three of our platforms.
Thanks!
Mark
prev parent reply other threads:[~2014-10-14 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 18:19 [PATCH 3/4] gnu: Add xfig Eric Bavier
2014-10-11 22:01 ` Ludovic Courtès
2014-10-12 21:34 ` Mark H Weaver
2014-10-13 6:23 ` John Darrington
2014-10-13 15:17 ` Eric Bavier
2014-10-13 19:27 ` John Darrington
2014-10-14 21:58 ` Mark H Weaver [this message]
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=87lhoi71pr.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=ericbavier@gmail.com \
--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 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).