unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add freeimage.
Date: Mon, 3 Nov 2014 10:29:01 +0100	[thread overview]
Message-ID: <20141103092901.GA7644@debian.eduroam.u-bordeaux.fr> (raw)
In-Reply-To: <87y4rsslop.fsf@gnu.org>

On Mon, Nov 03, 2014 at 10:00:38AM +0100, Ludovic Courtès wrote:
> Same problem as with Valgrind, so I would suggest disabling builds on
> MIPS, as done in commit 67a86d3.

Speaking of valgrind, how is transitivity of disabled builds handled,
on hydra and by the users?

I noticed that some packages do not build on mipss due to a dependency
on valgrind, for instance petsc-openmpi and petsc-complex-openmpi:
   http://hydra.gnu.org/build/132921
   http://hydra.gnu.org/build/132781
It was a bit confusing to me at first, since valgrind was not in the
"still failing jobs" tab, until I realised it was also not in the "still
succeeding jobs" tab and in fact disabled.

The two packages in question depend indirectly on valgrind via openmpi.
Now openmpi seems to be disabled for mips on hydra also, although it is
not explicitly disabled in the package recipe. These two other packages
are not disabled, however. So does this mean that the dependency graph
for disabled inputs is followed only to depth 1?

Andreas

  reply	other threads:[~2014-11-03  9:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 15:48 [PATCH] gnu: Add freeimage David Thompson
2014-11-01 16:59 ` Andreas Enge
2014-11-01 17:21   ` David Thompson
2014-11-02 17:26     ` Ludovic Courtès
2014-11-02 17:35       ` David Thompson
2014-11-02 17:46     ` Andreas Enge
2014-11-02 17:55       ` David Thompson
2014-11-02 21:10         ` Andreas Enge
2014-11-02 21:38           ` David Thompson
2014-11-03  9:00           ` Ludovic Courtès
2014-11-03  9:29             ` Andreas Enge [this message]
2014-11-03 20:28               ` Ludovic Courtès
2014-11-03 23:29           ` David Thompson
2014-11-04  9:50             ` Ludovic Courtès
2014-11-05  3:12               ` David Thompson

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=20141103092901.GA7644@debian.eduroam.u-bordeaux.fr \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).