Date: Sun, 16 Jun 2024 20:21:01 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 279777] net/openmpi, net/mpich: Suggestion to drop slurm-wlm dependency Message-ID: <bug-279777-7788-GLA31z1A5I@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279777-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-279777-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279777 --- Comment #5 from Jason W. Bacon <jwb@freebsd.org> --- Is anyone actually *running* SLURM on FreeBSD? It's been a while since I've tried, but I was unable to get anything later = than 20.02.7 working. Bug 276001 was my last attempt, and I only got as far as unbreaking the build. I don't recall the details of why the daemons wouldn= 't run. I have always used task/affinity, and it was no longer working last time I checked. FYI, I ported SLURM to FreeBSD. There are many features that never worked = due to Linuxisms (like parsing /proc files with scanf()), and the task of keepi= ng it working has grown with each new release. Upstream isn't interested in supporting other platforms, and in fact only provides significant support to paying customers. I finally gave up and started https://github.com/outpaddling/LPJS/. At any rate, making SLURM an unconditional dependency for MPI seemed questionable to me from the beginning, though I understood the desire to av= oid creating multiple packages. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279777-7788-GLA31z1A5I>