unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: forcing local build from a package definition
Date: Fri, 24 Oct 2014 18:10:41 +0200	[thread overview]
Message-ID: <CAKrPhPNSBWEHNee=RxQg9J1MXObadt2k6D8jJRowNOSO7M0K3g@mail.gmail.com> (raw)

Hi,

I'm preparing a package for ATLAS (Automatically Tuned Linear Algebra
Software).  The library provides functions from LAPACK which are automatically
speed optimized for the hardware on which the library is built (the
optimization takes place during the build phase).

My question is the following: is there a way to force a local build from a
package definition (without having to pass '--no-substitutes' to guix)?

If not, what do you think about explicitly stating in the description of the
package that it MUST be installed with the '--no-substitutes' flag and, if the
user does not do so, hydra may provide a package which does not run on the
user hardware?

Most other distributions deliver binary packages which have been compiled for
a very general CPU.  However, this not satisfactory since it results in a much
slower library.  Guix is in a nice position to provide a good performance
version of the library and I think we should do so.

Regards,
Fede

             reply	other threads:[~2014-10-24 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 16:10 Federico Beffa [this message]
2014-10-24 18:57 ` forcing local build from a package definition Eric Bavier
2014-10-24 21:41   ` Federico Beffa
2014-10-25  6:23   ` Federico Beffa
2014-10-25 22:25     ` Ludovic Courtès
2014-10-26  8:34       ` Federico Beffa
2014-10-26 13:59         ` Ludovic Courtès
2014-10-27 20:28           ` Federico Beffa

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='CAKrPhPNSBWEHNee=RxQg9J1MXObadt2k6D8jJRowNOSO7M0K3g@mail.gmail.com' \
    --to=beffa@ieee.org \
    --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).