Forums - Not able to install the nightly ONNX Runtime ARM64 python package

2 posts / 0 new
Last post
Not able to install the nightly ONNX Runtime ARM64 python package
vnrgoli1
Join Date: 4 Feb 24
Posts: 3
Posted: Fri, 2024-03-15 15:57

I am trying to install the QNN Execution Provider for ONNX Runtime and run a quantized model on Windows 11 Snapdragon box (Windows Dev Kit 2023) as mentioned on this URL : 

 
Errors popped up while installing the nightly ONNX Runtime ARM64 python package. The log is reporting some a dependency conflict. Please see the log below. Not sure how to remove those conflicting package versions or how to proceed.
 
Python and PIP are uptodate. 
 
I appreaciate any insight. 
 
Venkat.
 
-------------------------Pip install Log at the end------------------ 
 
---------------------------------------------------------------6.5/6.5 MB 37.9 MB/s eta 0:00:00
ERROR: Cannot install ort-nightly-qnn==1.18.0.dev20240213001, ort-nightly-qnn==1.18.0.dev20240213003, ort-nightly-qnn==1.18.0.dev20240214003, ort-nightly-qnn==1.18.0.dev20240215004, ort-nightly-qnn==1.18.0.dev20240216004, ort-nightly-qnn==1.18.0.dev20240217001, ort-nightly-qnn==1.18.0.dev20240218001, ort-nightly-qnn==1.18.0.dev20240219001, ort-nightly-qnn==1.18.0.dev20240221006, ort-nightly-qnn==1.18.0.dev20240223001, ort-nightly-qnn==1.18.0.dev20240223005, ort-nightly-qnn==1.18.0.dev20240224001, ort-nightly-qnn==1.18.0.dev20240225001, ort-nightly-qnn==1.18.0.dev20240226004, ort-nightly-qnn==1.18.0.dev20240227006, ort-nightly-qnn==1.18.0.dev20240228007, ort-nightly-qnn==1.18.0.dev20240229007, ort-nightly-qnn==1.18.0.dev20240301005, ort-nightly-qnn==1.18.0.dev20240304002, ort-nightly-qnn==1.18.0.dev20240305002, ort-nightly-qnn==1.18.0.dev20240306006, ort-nightly-qnn==1.18.0.dev20240307004, ort-nightly-qnn==1.18.0.dev20240311001, ort-nightly-qnn==1.18.0.dev20240312004, ort-nightly-qnn==1.18.0.dev20240313005 and ort-nightly-qnn==1.18.0.dev20240314003 because these package versions have conflicting dependencies.
 
The conflict is caused by:
    ort-nightly-qnn 1.18.0.dev20240314003 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240313005 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240312004 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240311001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240307004 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240306006 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240305002 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240304002 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240301005 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240229007 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240228007 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240227006 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240226004 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240225001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240224001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240223005 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240223001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240221006 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240219001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240218001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240217001 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240216004 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240215004 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240214003 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240213003 depends on coloredlogs
    ort-nightly-qnn 1.18.0.dev20240213001 depends on coloredlogs
 
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
 
 

 

  • Up0
  • Down0
kuntong
Join Date: 10 Apr 24
Posts: 1
Posted: Wed, 2024-04-10 02:30

Hi, the same problem, have you solved it? 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.