-
Notifications
You must be signed in to change notification settings - Fork 537
Installing from source on Google Cloud Ubuntu 24.04 #8311
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
Comments
What is the version of Trying to figure out what input is different between two machines. Can you give me full stack trace as well? |
Stack trace as follows:
|
These are the four most recent attempts to try and resolve this. These all produce the same error.
|
What is the input command/string here? |
I'm not sure what the input is. Would that be a value passed from install_executorch.py to setuptools? |
If I were to guess, this is coming from here. And I guess I can try to repro |
Summary: This was not handled and run into `int("")` failing. Test Plan: Locally tested installing with `export DEBUG=""`. Reviewers: Subscribers: Tasks: Resolves #8311 Tags:
Try the PR? |
Yes. That resolved the issue. This now installs on a Google Cloud machine with Ubuntu 24.04. Not so relevant to the issue, but for full reproducibility I used g++ (13.3.0), clang++ (18.1.3) and the latest setuptools (75.8.0). |
Sorry to bother with a minor install issue.
I can install from source on my local machine just fine. However on a Google Cloud machine I have been unable to troubleshoot the following error:
The Google Cloud machine is running Ubuntu 24.04 and I have installed g++ (13.3.0) and clang++ (18.1.3).
For the installation I followed the guide linked below, using a Python 3.10.0 virtual environment. https://pytorch.org/executorch/main/getting-started-setup
I am only wanting to export a pte file for a model that is too large for my local machine. The version available through pip doesn't seem to be able to do this.
Do you have other troubleshooting tips?
cc @larryliu0820
The text was updated successfully, but these errors were encountered: