-
Notifications
You must be signed in to change notification settings - Fork 35
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
Problems in built-from-source pytorch with USE_DEPLOY=1 in Ubuntu #123
Comments
Did you build pytorch in
and then build multipy. You can also use multipy directly from pytorch as the rst you found states. The primary reason we have the build from source instructions here is for development on multipy. |
This issue is what I encountered when I was trying to use multipy directly from pytorch. I followed this rst. Now I have m it and managed to build pytorch from source with USE_DEPLOY=1. The problem seems to be that I didn't install the complete list of dependencies for CPython. However, when trying the example in this rst, it reports an error at the stage of So, do you by chance know why this tutorial example doesn't work? Also what is the difference between torch::deploy and multipy the out-of-core repo. Which one is the one that you will focus on in the future? Thanks! Here is the full message:
|
@KexinFeng we've completely revamped the install process so it should be a lot simpler and not require building torch from source. Does the new install process work better for you? |
📚 The doc issue
Hi,
I'm trying the tutorial example of deploy and aim to package a model and do inference in C++. But I ran into a problems when working with build-from-source pytorch. There are following issue:
The error message is the following. Note that I have used CPU built by setting the environment variable as
export USE_CUDA=0
.I have also set
export USE_DEPLOY=1
following (deploy
tutorial)[https://pytorch.org/docs/stable/deploy.html#loading-and-running-the-model-in-c].Any help will be appreciated!
Here is the system info:
Suggest a potential alternative/fix
No response
cc @wconstab
The text was updated successfully, but these errors were encountered: