unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add Julia.
Date: Sun, 29 Mar 2015 15:21:50 +0200	[thread overview]
Message-ID: <87619k0wi9.fsf@gnu.org> (raw)
In-Reply-To: <87619nqx5f.fsf@mango.localdomain> (Ricardo Wurmus's message of "Thu, 26 Mar 2015 22:14:20 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> Mark H Weaver writes:
>
>> When reading this the first time, somehow I managed to miss the fact
>> that users will have to set OPENBLAS_CORETYPE to their CPU type.  Does
>> that mean that openblas is unable to detect the CPU type automatically?
>> What does it do if OPENBLAS_CORETYPE is unset?
>>
>> Will we have to set it during the build of packages that use openblas,
>> such as Julia?
>
> It appears that this is not necessary.  I downloaded the OpenBLAS
> substitute from hydra and built Julia locally on my notebook.  Julia
> runs without problems.  It appears that OpenBLAS does detect the CPU
> type automatically.

That’s good news.

> (There is a problem with our Julia package, which made me build Julia
> myself.  Also seems to be related to CPU tuning.  Passing a make-flag to
> force a generic build should fix this.)

OK.

Ludo’.

      reply	other threads:[~2015-03-29 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 11:16 [PATCH] Add Julia Ricardo Wurmus
2015-03-23  9:29 ` Ludovic Courtès
2015-03-23 21:35 ` Mark H Weaver
2015-03-24 14:56   ` Mark H Weaver
2015-03-24 17:14     ` Ricardo Wurmus
2015-03-24 20:45       ` Ludovic Courtès
2015-03-25 16:20       ` Mark H Weaver
2015-03-25 18:24         ` Ricardo Wurmus
2015-03-25 21:00           ` Mark H Weaver
2015-03-26 15:19         ` Mark H Weaver
2015-03-26 16:58           ` Ludovic Courtès
2015-03-26 21:14           ` Ricardo Wurmus
2015-03-29 13:21             ` Ludovic Courtès [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=87619k0wi9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).