michaelwcl opened a new issue, #18388:
URL: https://github.com/apache/tvm/issues/18388

   Thanks for participating in the TVM community! We use https://discuss.tvm.ai 
for any general usage questions and discussions. The issue tracker is used for 
actionable items such as feature proposals discussion, roadmaps, and bug 
tracking.  You are always welcomed to post on the forum first :smile_cat:
   
   Issues that are inactive for a period of time may get closed. We adopt this 
policy so that we won't lose track of actionable issues that may fall at the 
bottom of the pile. Feel free to reopen a new one if you feel there is an 
additional problem that needs attention when an old one gets closed.
   
   ### Expected behavior
   
   A successful install via pip and being able to the tvm package as needed.
   
   ### Actual behavior
   
   Build process seems to finish but with a lot of warnings, and tvm-ffi cannot 
be installed from /path/to/tvm/build/3rdparty/tvm-ffi via pip.
   Error: "ERROR: Directory '.' is not installable. Neither 'setup.py' nor 
'pyproject.toml' found."
   
   As a sidenote, I've tried 0.21 and 0.22 as well, which I downloaded as 
tarballs from the github releases. It seems like the build from source process 
documented on the website no loner applies to those older versions.
   
   ### Environment
   
   Ubuntu 24.04, tvm version is the latest (cloned the repo on Oct 23, 2025). 
   
   ### Steps to reproduce
   
   Follow the instructions on 
https://tvm.apache.org/docs/install/from_source.html
   
   ### Triage
   
   Please refer to the list of label tags 
[here](https://github.com/apache/tvm/wiki/Issue-Triage-Labels) to find the 
relevant tags and add them below in a bullet format (example below).
   
   * needs-triage
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to