From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add Julia.
Date: Tue, 24 Mar 2015 18:14:06 +0100 [thread overview]
Message-ID: <idjvbhq1foh.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87pp7yphom.fsf@netris.org>
Mark H Weaver writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>>
>>> From 41550ffafa8da05b2cf8dfad66d44e6f43c9042c Mon Sep 17 00:00:00 2001
>>> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
>>> Date: Fri, 20 Mar 2015 11:26:23 +0100
>>> Subject: [PATCH 2/2] gnu: Add Julia.
>>>
>>> * gnu/packages/julia.scm: New file.
>>> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.
>>
>> Hydra was unable to successfully build Julia on any platform. See:
>>
>> http://hydra.gnu.org/build/339221
>> http://hydra.gnu.org/build/339192
>
> The illegal instruction errors are in openblas, which is marked
> non-substitutable because it apparently builds itself customized to the
> CPU on the build machine. So, I guess openblas might have been built on
> a build slave with more processor features than the one used to build
> Julia.
>
> Perhaps the answer is that Julia shouldn't be built by Hydra, because
> one of its transitive inputs is non-substitutable.
I encountered build failures trying to install openblas on a virtual
machine (works fine on my workstation). While looking for a solution I
stumbled upon the openblas make flag "DYNAMIC_ARCH=1" which asks
openblas to build modules for all(?) supported CPUs.
After modifying the openblas package in this manner it was built on the
virtual machine without issues and I could use it with Julia (so far
without problems).
May I suggest adding passing the "DYNAMIC_ARCH=1" flag in openblas
instead of propagating non-substitutability to Julia? When built with
"DYNAMIC_ARCH=1" the CPU type can be picked with the environment
variable OPENBLAS_CORETYPE=<type>. If I'm not mistaken this makes
substitutions for openblas possible.
What do you think?
~~ Ricardo
next prev parent reply other threads:[~2015-03-24 17:14 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 [this message]
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
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=idjvbhq1foh.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--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.