PyTorch: build with external gloo #40759
Conversation
|
Hi @adamjstewart! I noticed that the following package(s) don't yet have maintainers:
Are you interested in adopting any of these package(s)? If so, simply add the following to the package class: maintainers("adamjstewart")If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with $ spack blame glooThank you for your help! Please don't add maintainers without their consent. You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer. |
|
Builds fine for PyTorch 2.1 but not for 2.0, and horovod does not yet support 2.1 so we can't avoid building 2.0 in CI without dropping horovod. @tgaddair @thomas-bouvier any thoughts on how long it will take to fix horovod/horovod#3996? |
|
@adamjstewart Feel free to merge (not sure if you're waiting for further reviews on this PR). |
|
@adamjstewart I was waiting for #40057 to be merged, working on it! |
adamjstewart
force-pushed
the
packages/gloo
branch
from
f0454fe
to
5d2ea05
Compare
* PyTorch: build with external gloo * Fix gloo compilation with GCC 11 * undeprecate * py-torch+cuda+gloo requires gloo+cuda
* PyTorch: build with external gloo * Fix gloo compilation with GCC 11 * undeprecate * py-torch+cuda+gloo requires gloo+cuda
* PyTorch: build with external gloo * Fix gloo compilation with GCC 11 * undeprecate * py-torch+cuda+gloo requires gloo+cuda
Trying to get PyTorch to build entirely with Spack-installed deps.