From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Love Subject: Re: Open MPI keeps references to GCC, GFortran, etc. Date: Mon, 31 Jul 2017 19:49:17 +0100 Message-ID: <87fudcbfwy.fsf@i-ulialbion.it.manchester.ac.uk> References: <87vame5jgd.fsf@gnu.org> <87d18mhu2f.fsf@i-ulialbion.it.manchester.ac.uk> <87poclm16e.fsf@inria.fr> <87ini8dip7.fsf@i-ulialbion.it.manchester.ac.uk> <878tj4675o.fsf@inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59510) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcFkr-0005ZS-Uf for guix-devel@gnu.org; Mon, 31 Jul 2017 14:49:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dcFkm-0000Hj-Vq for guix-devel@gnu.org; Mon, 31 Jul 2017 14:49:26 -0400 Received: from tranquility.mcc.ac.uk ([130.88.200.145]:50327) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dcFkm-0000Gb-Ni for guix-devel@gnu.org; Mon, 31 Jul 2017 14:49:20 -0400 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") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel , Ricardo Wurmus , Eric Bavier Ludovic Court=C3=A8s writes: > My intent was to remove the *run-time* dependency of openmpi on gcc & > co. (as returned by =E2=80=98guix gc --references=E2=80=99 or =E2=80=98gu= ix size openmpi=E2=80=99.) 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=E2=80=99t make sense to do this.) >> >> But they're not compatible, which is a real problem > > It shouldn=E2=80=99t be a problem if you do something like shown above, t= hen. 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=E2=80=99ve 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.