-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trying to build torch_migraphx I get errors. I got those solved (see below) but running tests mostly fail. #129
Comments
I think I solved it. |
After installing cmake with sudo apt-get install cmake I get a different failure.
|
I tried "pip install pybind11" and while that installed something, that did not change the errors. |
I uninstalled from pip and tried to build pybind11 directly from https://github.com/pybind/pybind11 This reported: Successfully installed pybind11-2.13.0.dev1 This did not change the error. This seems like a common problem here Since I'm not used to these packages, I have no idea how to undo whatever running "pip install ." did in the pybind11 git clone, nor how to fix the installation! |
Finally solve it with: SO all of the steps I needed to get it to build were:
|
Now that it built I tested it. Most tests failed.
|
Thanks to your help, I managed to get it installed past a lot of these errors too. Not much improvement on the tests:
|
Problem Description
I tried to build torch_migraphx, but got an error.
Note that even though it says that it can't find the torch module, in any python code I write it does import as 2.4.0.dev20240604+rocm6.1
Note that the form didn't let me choose my actual card which is a Radeon Instinct MI50 32 gb which reports as
Error output:
Additional Information
I installed the drivers with apt get-install, nothing custom or fancy.
And I got pytorch from the nightly because that's the only place where you can get support for ROCm 6.1
And I got ONNX from /rocm/manylinux/rocm-rel-6.1/ even though the documentation still points at 6.0 libraries instead
The text was updated successfully, but these errors were encountered: