all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/4] gnu: Add xfig.
Date: Mon, 13 Oct 2014 08:23:14 +0200	[thread overview]
Message-ID: <20141013062313.GA16250@jocasta.intra> (raw)
In-Reply-To: <87egudx991.fsf@netris.org>

On Sun, Oct 12, 2014 at 05:34:34PM -0400, Mark H Weaver wrote:
     
     Eric Bavier <ericbavier@gmail.com> writes:
     
     > From fca4924a98e06ec0d2877b14f074515a2a970605 Mon Sep 17 00:00:00 2001
     > From: Eric Bavier <bavier@member.fsf.org>
     > Date: Fri, 10 Oct 2014 13:10:42 -0500
     > Subject: [PATCH 3/4] gnu: Add xfig.
     
     Hydra reports that xfig only builds successfully on x86_64.  It fails on
     i686 and mips64el.  Can you investigate?
     
     
Looking at the mass of subsitions in xfig, it seems to me that xfig is fighting 
against imake.   In particular I see that imake sets the PROJECT_ROOT to /gnu/store/*imake/
which is wrong for every package except Imake itself.

It has been a few years since I used imake, but I seem to remember there was the
possibility to have a "vendor" specific control file.  In our case Guix is the 
vendor, so perhaps we should have a guix.cf file in imake.  However, since this 
would have to be provided by each package which uses imake.  Perhaps it would be
better to have a imake-build-system which generated it dynamically.

J'





-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

  reply	other threads:[~2014-10-13  6:23 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 [this message]
2014-10-13 15:17     ` Eric Bavier
2014-10-13 19:27       ` John Darrington
2014-10-14 21:58       ` Mark H Weaver

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=20141013062313.GA16250@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.