This package contains the kernel module and some userland tools for Myricoms Myrinet-2000 interconnect hardware (www.myri.com). I'd suggest sys-cluster as this appears to be where the openib driver is as well. Tested the compile on the keworded archs, and against the actual hardware on ppc64 only. This provides the gm referenced in bug 166787. Reproducible: Always
Created attachment 124007 [details] gm-2.0.26.ebuild
Created attachment 124008 [details] gm-conf.d
Created attachment 124011 [details] gm-init.d This is a re-write of the upstream init script, trimmed down quite a bit.
It's missing DEPENDS and RDEPENDS, and it looks like it should either depend on Torque (>=2.0?) or support a "torque" useflag. Wasn't Myricom in the kernel anyways (CONFIG_MYRI10GE) ? Maybe you want to just put the userland tools in there (Just guessing, I don't know that much about myricom hardware to actually make a statement) (In reply to comment #1) > Created an attachment (id=124007) [edit] > gm-2.0.26.ebuild >
(In reply to comment #4) > It's missing DEPENDS and RDEPENDS, and it looks like it should either depend on > Torque (>=2.0?) or support a "torque" useflag. I believe that all the depends are covered in the profile, although I'm fuzzy on this. We need libc, linux-sources and gcc. Myrinet doesn't have any reliance on Torque either, although jobs running in Torque may use Myrinet as the transport layer. > Wasn't Myricom in the kernel anyways (CONFIG_MYRI10GE) ? That's the newer hardware, Myri-10G, whereas this driver covers Myrinet-2000.
This package does not meet the current criteria needed to be a viable candidate for the Portage tree since the upstream sources are no longer available at the location provided by the ebuild. This criteria is currently listed at the following URL: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/Maintainer_Wanted Metric: Upstream status: Exists; "Package must still be available and fetchable (did it move to github, bitbucket, ...?)" If you (or another user) are still wanting this package to make it into the Portage tree please let us know by re-opening this bug and include a new usable upstream source. Sadly, until that time we cannot move forward with this ebuild. Tom D
