From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>,
Eric Bavier <bavier@member.fsf.org>
Subject: Re: Open MPI keeps references to GCC, GFortran, etc.
Date: Mon, 31 Jul 2017 19:49:17 +0100 [thread overview]
Message-ID: <87fudcbfwy.fsf@i-ulialbion.it.manchester.ac.uk> (raw)
In-Reply-To: <878tj4675o.fsf@inria.fr> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Mon, 31 Jul 2017 15:57:23 +0200")
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> My intent was to remove the *run-time* dependency of openmpi on gcc &
> co. (as returned by ‘guix gc --references’ or ‘guix size openmpi’.)
OK, I can send that, though there might still be a case for a separate
runtime output.
>> Looking at the packaging more closely, I think it needs, or should have,
>> various changes. --enable-static clobbers dynamically-loaded MCA
>> components, which I think is is a non-starter. One question I have is
>> why are builtin atomics turned on? They normally aren't, and I don't
>> know what the consequences are.
>
> No idea, you probably know better than me.
I'm afraid not. It's a question for whoever enabled it.
>> I assume the store is intended to be on a shared filesystem which
>> compute nodes don't duplicate, which helps with space, but I don't think
>> that should be required. The stateless systems I've set up used a
>> separate compute node image which was much smaller than the login node
>> one by omitting non-runtime rpms.
>
> Yeah the store is typically meant to be shared over NFS or similar. On
> the topic of setting up Guix on a cluster, you might want to check:
>
> https://elephly.net/posts/2015-04-17-gnu-guix.html
> https://hal.inria.fr/hal-01161771/en
I think I've read both of them, and I'd argue with some of what they say
-- but I shouldn't here.
>>> I suppose you could to:
>>>
>>> (define openmpi-with-gfortran7
>>> (package
>>> (inherit openmpi)
>>> (name "openmpi-gfortran7")
>>> (inputs `(("gfortran" ,gfortran-7)
>>> ,@(alist-delete "gfortran" (package-inputs openmpi))))))
>>
>> Right.
>>
>>> (That said, if the .mod files are compatible among gfortran versions, it
>>> probably doesn’t make sense to do this.)
>>
>> But they're not compatible, which is a real problem
>
> It shouldn’t be a problem if you do something like shown above, then.
It's a general problem that means you have to do something like the
above (which presumably makes the closure big again).
>> By the way, I don't want to be an HPC bigot, but HPC requirements seem
>> to be largely a superset of most others, and applicable in other areas.
>
> Agreed! And I think Guix also makes it easier to meet some of the HPC
> requirements, from what I’ve seen.
Yes, but there are clear trades-off, and from what I've seen the promise
isn't really realized yet. I hope it will be, with more engineering
effort, and thanks for all the effort on it.
prev parent reply other threads:[~2017-07-31 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:15 Open MPI keeps references to GCC, GFortran, etc Ludovic Courtès
2017-07-27 13:45 ` Dave Love
2017-07-28 8:10 ` Ludovic Courtès
2017-07-31 10:06 ` Dave Love
2017-07-31 13:57 ` Ludovic Courtès
2017-07-31 18:49 ` Dave Love [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=87fudcbfwy.fsf@i-ulialbion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=bavier@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
--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).