<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Getting openvino open source 2022/1.1 to work on Ubuntu 22.04 in Intel® Distribution of OpenVINO™ Toolkit</title>
    <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498584#M29629</link>
    <description>As I mentioned in a previous post. I am trying a parallel track building using Ubuntu 20.04 in QEMU/KVM. I have now been succesful with that approach.</description>
    <pubDate>Fri, 23 Jun 2023 15:33:05 GMT</pubDate>
    <dc:creator>wearyhacker</dc:creator>
    <dc:date>2023-06-23T15:33:05Z</dc:date>
    <item>
      <title>Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497348#M29589</link>
      <description>&lt;P&gt;I am trying to get openvino 2022/1.1 to work on Ubuntu 22.0 and talk to my NCS2 stick I have run into a problem. This is where I have got to so far.&lt;/P&gt;&lt;P&gt;1. Cloned the openvino repo.&lt;BR /&gt;2. Checked out the releases/2022/1.1 branch.&lt;BR /&gt;3. Initialised the submodules.&lt;BR /&gt;4. The build encountered a number compiler warnings that were treated as errors.&lt;BR /&gt;5. I fixed the error in src/core/src/type/bfloat16.cpp.&lt;BR /&gt;`@@ -57,7 +57,7 @@ size_t bfloat16::size() const {&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;bfloat16::operator float() const {&lt;BR /&gt;- uint32_t tmp = (static_cast&amp;lt;uint32_t&amp;gt;(m_value) &amp;lt;&amp;lt; 16);&lt;BR /&gt;+ static uint32_t tmp = (static_cast&amp;lt;uint32_t&amp;gt;(m_value) &amp;lt;&amp;lt; 16);&lt;BR /&gt;const float* f = reinterpret_cast&amp;lt;const float*&amp;gt;(&amp;amp;tmp);&lt;BR /&gt;return *f;&lt;BR /&gt;}`&lt;/P&gt;&lt;P&gt;6. I realised all the other errors were in a template in single include file and that it would not be easy to fix. So I turned off the treat warnings as errors flag in the CMake config.&lt;BR /&gt;7. I stuck my head in a bucket of cold water.&lt;BR /&gt;8. I got as far as building the python wheels and hit a problem with the numpy version. So I took a chance and modified src/bindings/python/requirements.txt to remove the top limit on the numpy version. This caused an error in src/bindings/python/wheel/CMakeLists.txt.&lt;/P&gt;&lt;P&gt;`@@ -33,7 +33,7 @@ endforeach()&lt;BR /&gt;&lt;BR /&gt;execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import wheel.bdist_wheel ; print(f'{wheel.bdist_wheel.get_abi_tag()}')" OUTPUT_VARIABLE PYTHON_ABI)&lt;BR /&gt;execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import wheel.vendored.packaging.tags as tags ; print(f'{tags.interpreter_name()}{tags.interpreter_version()}')" OUTPUT_VARIABLE INTERPRETER)&lt;BR /&gt;-execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import wheel.vendored.packaging.tags as tags ; print(f'{next(tags._platform_tags())}')" OUTPUT_VARIABLE WHEEL_PLATFORM)&lt;BR /&gt;+execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import wheel.vendored.packaging.tags as tags ; print(f'{next(tags.platform_tags())}')" OUTPUT_VARIABLE WHEEL_PLATFORM)&lt;BR /&gt;string(STRIP ${PYTHON_ABI} PYTHON_ABI)&lt;BR /&gt;string(STRIP ${INTERPRETER} INTERPRETER)&lt;BR /&gt;string(STRIP ${WHEEL_PLATFORM} WHEEL_PLATFORM)&lt;BR /&gt;`&lt;/P&gt;&lt;P&gt;9. This finally got everything to build.&lt;BR /&gt;10. But as I expected there was a runtime error!&lt;/P&gt;&lt;P&gt;`Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linux&lt;BR /&gt;Type "help", "copyright", "credits" or "license" for more information.&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; from openvino.runtime import Core&lt;BR /&gt;/home/roger/.local/lib/python3.10/site-packages/openvino/runtime/utils/types.py:24: FutureWarning: In the future `np.bool` will be defined as the corresponding NumPy scalar.&lt;BR /&gt;(Type.boolean, np.bool),&lt;BR /&gt;Traceback (most recent call last):&lt;BR /&gt;File "&amp;lt;stdin&amp;gt;", line 1, in &amp;lt;module&amp;gt;&lt;BR /&gt;File "/home/roger/.local/lib/python3.10/site-packages/openvino/runtime/__init__.py", line 38, in &amp;lt;module&amp;gt;&lt;BR /&gt;from openvino.runtime.ie_api import Core&lt;BR /&gt;File "/home/roger/.local/lib/python3.10/site-packages/openvino/runtime/ie_api.py", line 16, in &amp;lt;module&amp;gt;&lt;BR /&gt;from openvino.runtime.utils.types import get_dtype&lt;BR /&gt;File "/home/roger/.local/lib/python3.10/site-packages/openvino/runtime/utils/types.py", line 24, in &amp;lt;module&amp;gt;&lt;BR /&gt;(Type.boolean, np.bool),&lt;BR /&gt;File "/home/roger/.local/lib/python3.10/site-packages/numpy/__init__.py", line 313, in __getattr__&lt;BR /&gt;raise AttributeError(__former_attrs__[attr])&lt;BR /&gt;AttributeError: module 'numpy' has no attribute 'bool'.&lt;BR /&gt;`np.bool` was a deprecated alias for the builtin `bool`. To avoid this error in existing code, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.&lt;BR /&gt;The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:&lt;BR /&gt;&lt;A href="https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations" target="_blank" rel="noopener"&gt;https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations&lt;/A&gt;. Did you mean: 'bool_'?&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;`&lt;/P&gt;&lt;P&gt;Numpy strikes again.&lt;/P&gt;&lt;P&gt;Has anyone been down this path before?&lt;BR /&gt;Has anyone got any ideas on how to get past with minimal intervention in the source?&lt;/P&gt;&lt;P&gt;Help!&lt;/P&gt;&lt;P&gt;Roger&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 09:09:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497348#M29589</guid>
      <dc:creator>wearyhacker</dc:creator>
      <dc:date>2023-06-20T09:09:27Z</dc:date>
    </item>
    <item>
      <title>Re:Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497637#M29596</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;to clarify, could you share your build commands till the point of error? It seems that you only shared your troubleshooting commands.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Jun 2023 04:14:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497637#M29596</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-06-21T04:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497689#M29601</link>
      <description>&lt;P&gt;Here is the history of what I did. I edited it for clarity.&lt;/P&gt;&lt;P&gt;git clone &lt;A href="https://github.com/openvinotoolkit/openvino.git" target="_blank"&gt;https://github.com/openvinotoolkit/openvino.git&lt;/A&gt;&lt;BR /&gt;cd openvino&lt;BR /&gt;git checkout releases/2022/1.1&lt;BR /&gt;git submodule update --init --recursive&lt;BR /&gt;mkdir build&lt;BR /&gt;cd build&lt;BR /&gt;cmake -DCMAKE_BUILD_TYPE=Release&lt;BR /&gt;make --jobs=$(nproc --all)&lt;/P&gt;&lt;P&gt;This gave a number of warnings that were treated as errors. I fixed those as I detailed in in my original post.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have now started a parallel track building using Ubuntu 20.04 in QEMU/KVM. I have run into the buffers on that track with openvino failing to find the ncs2 device even though it shows up in lsusb. But that is a question for a new thread!&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 08:13:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1497689#M29601</guid>
      <dc:creator>wearyhacker</dc:creator>
      <dc:date>2023-06-21T08:13:24Z</dc:date>
    </item>
    <item>
      <title>Re: Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498110#M29609</link>
      <description>&lt;P&gt;Generally,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;OpenVINO 2022.1.1 is officially validated only on these Ubuntu versions:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Ubuntu 18.04 (64-bit) with default GCC 7.5.0&lt;/LI&gt;
&lt;LI&gt;Ubuntu 20.04 (64-bit) with default GCC 9.3.0&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You may refer to the validated software&amp;nbsp;&lt;A href="https://docs.openvino.ai/2022.1/openvino_docs_install_guides_installing_openvino_from_archive_linux.html" target="_self"&gt;here&lt;/A&gt; and &lt;A href="https://github.com/openvinotoolkit/openvino/blob/master/docs/dev/build_linux.md" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also noticed that building &lt;STRONG&gt;OV 2022.1.1 in Ubuntu 22.04&lt;/STRONG&gt;&amp;nbsp;produced some errors which is expected since &lt;STRONG&gt;it's not officially validated&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_1remote.png" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/42723iB939168C65E85504/image-size/medium?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="_1remote.png" alt="_1remote.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To ensure that the OV 2022.1.1 really works, it is recommended to &lt;STRONG&gt;use the Ubuntu version that is officially validated&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_1.PNG" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/42724i125C728A788C0DBB/image-size/medium?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="_1.PNG" alt="_1.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_4.PNG" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/42725iE873CF7BADEA1BB6/image-size/medium?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="_4.PNG" alt="_4.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_5.PNG" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/42726i80215E56724110A3/image-size/medium?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="_5.PNG" alt="_5.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any specific reason to be using Ubuntu 22.04 with OpenVINO 2022.1?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cordially,&lt;/P&gt;
&lt;P&gt;Iffa&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2023 09:20:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498110#M29609</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-06-22T09:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498114#M29611</link>
      <description>&lt;P&gt;I need 2022.1 because I want to drive a NCS2 Myriad X.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2023 09:49:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498114#M29611</guid>
      <dc:creator>wearyhacker</dc:creator>
      <dc:date>2023-06-22T09:49:45Z</dc:date>
    </item>
    <item>
      <title>Re:Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498425#M29617</link>
      <description>&lt;P&gt;Yes I understand that you need OV 2022.1 because of VPU/NCS2.&lt;/P&gt;&lt;P&gt;You could &lt;STRONG&gt;use Ubuntu 20.04&lt;/STRONG&gt; (officially validated by OpenVINO) instead 22.04 with it, unless you have specific reason for using Ubuntu 22.04?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jun 2023 00:21:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498425#M29617</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-06-23T00:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498584#M29629</link>
      <description>As I mentioned in a previous post. I am trying a parallel track building using Ubuntu 20.04 in QEMU/KVM. I have now been succesful with that approach.</description>
      <pubDate>Fri, 23 Jun 2023 15:33:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1498584#M29629</guid>
      <dc:creator>wearyhacker</dc:creator>
      <dc:date>2023-06-23T15:33:05Z</dc:date>
    </item>
    <item>
      <title>Re:Getting openvino open source 2022/1.1 to work on Ubuntu 22.04</title>
      <link>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1499841#M29664</link>
      <description>&lt;P&gt;Glad that your issue is resolved.&lt;/P&gt;&lt;P&gt;Thanks for informing.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I'm proceeding to close this thread.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 11pt;"&gt;Intel will no longer monitor this thread since this issue has been resolved.&amp;nbsp;If you need any additional information from Intel, please submit a new question.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jun 2023 05:12:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/Getting-openvino-open-source-2022-1-1-to-work-on-Ubuntu-22-04/m-p/1499841#M29664</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-06-28T05:12:56Z</dc:date>
    </item>
  </channel>
</rss>

