[PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

[PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

[Jason Wessel]

There are a number of other recipes outside oe-core that depend on
alsa-lib and the rpm4 dependencies resolve sometimes to include
alsa-lib and the packages in the other layers fail to install because
the dependency cannot be resolved, despite the fact that libasound is
installed.

The simple is to add an RPROVIDES for alsa-lib to libasound which
provides all the shared objects for alsa.

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
 meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
index c5bf107..f7f01e8 100644
--- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
+++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
@@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
 FILES_alsa-conf = "${datadir}/alsa/"
 
 RDEPENDS_libasound = "alsa-conf"
+RPROVIDES_libasound = "alsa-lib"
 
 # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
 # alsa-lib package doesn't exist. libasound is the real library package.
-- 
2.7.4

[PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

[Jason Wessel]

When using an image built with the Yocto Project which has a compiler
and all the required libraries, projects such as caffe for the
Movidius SDK which use python3 and boost fail to build because they
look for libboost_python.so.  The error that cmake returns doesn't
even point to the fact that this is why the configuration fails.

Example showing the problem with the missing symlink:
================
  git clone https://github.com/weiliu89/caffe.git
  cd caffe
  mkdir build
  cd build
  cmake -DBLAS=Open ..

-- Configuring done
CMake Error at CMakeLists.txt:85 (add_dependencies):
  The dependency target "pycaffe" of target "pytest" does not exist.
================

Conditionally creating the link when building python3 support into
boost is all that is needed.

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
 meta/recipes-support/boost/boost.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
index 0461ec6..c53edf7 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -195,6 +195,9 @@ do_install() {
 		fi
 	done
 
+	if [ -e ${D}${libdir}/libboost_python3.so ]; then
+		ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
+	fi
 }
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.7.4

[PATCH 3/3] python3: Fix purelib install and runtime paths

[Jason Wessel]

oe-core commit: 45afadf0b6 fixed the pip problem with purelib for
python2, even though the the patch stated it was for python3.  This
patch addresses the purelib problem for python3.

If you install the package python3-pip you will have a pip3 binary
where you can see the problem on the device easily where the modules
install into the incorrect area and are not able to be referenced by
python3 at all.

Example error:
   pip3 install imutils
   pip3 list |grep imutils || echo ERROR no imutils
      ERROR no imutils
   python3 -c 'import imutils'
     Traceback (most recent call last):
       File "<string>", line 1, in <module>
     ImportError: No module named 'imutils'

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
 .../python/python3/python-3.3-multilib.patch        | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/meta/recipes-devtools/python/python3/python-3.3-multilib.patch b/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
index 77da615..cc35dc1 100644
--- a/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
+++ b/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
@@ -52,11 +52,13 @@ Index: Python-3.5.4/Lib/distutils/command/install.py
  WINDOWS_SCHEME = {
      'purelib': '$base/Lib/site-packages',
      'platlib': '$base/Lib/site-packages',
-@@ -30,7 +32,7 @@ WINDOWS_SCHEME = {
+@@ -29,8 +31,8 @@ WINDOWS_SCHEME = {
+ 
  INSTALL_SCHEMES = {
      'unix_prefix': {
-         'purelib': '$base/lib/python$py_version_short/site-packages',
+-        'purelib': '$base/lib/python$py_version_short/site-packages',
 -        'platlib': '$platbase/lib/python$py_version_short/site-packages',
++        'purelib': '$platbase/'+libname+'/python$py_version_short/site-packages',
 +        'platlib': '$platbase/'+libname+'/python$py_version_short/site-packages',
          'headers': '$base/include/python$py_version_short$abiflags/$dist_name',
          'scripts': '$base/bin',
@@ -103,10 +105,11 @@ Index: Python-3.5.4/Lib/sysconfig.py
      'posix_prefix': {
 -        'stdlib': '{installed_base}/lib/python{py_version_short}',
 -        'platstdlib': '{platbase}/lib/python{py_version_short}',
+-        'purelib': '{base}/lib/python{py_version_short}/site-packages',
+-        'platlib': '{platbase}/lib/python{py_version_short}/site-packages',
 +        'stdlib': '{installed_base}/'+sys.lib+'/python{py_version_short}',
 +        'platstdlib': '{platbase}/'+sys.lib+'/python{py_version_short}',
-         'purelib': '{base}/lib/python{py_version_short}/site-packages',
--        'platlib': '{platbase}/lib/python{py_version_short}/site-packages',
++        'purelib': '{platbase}/'+sys.lib+'/python{py_version_short}/site-packages',
 +        'platlib': '{platbase}/'+sys.lib+'/python{py_version_short}/site-packages',
          'include':
              '{installed_base}/include/python{py_version_short}{abiflags}',
@@ -117,10 +120,11 @@ Index: Python-3.5.4/Lib/sysconfig.py
      'posix_home': {
 -        'stdlib': '{installed_base}/lib/python',
 -        'platstdlib': '{base}/lib/python',
+-        'purelib': '{base}/lib/python',
+-        'platlib': '{base}/lib/python',
 +        'stdlib': '{installed_base}/'+sys.lib+'/python',
 +        'platstdlib': '{base}/'+sys.lib+'/python',
-         'purelib': '{base}/lib/python',
--        'platlib': '{base}/lib/python',
++        'purelib': '{base}/'+sys.lib+'/python',
 +        'platlib': '{base}/'+sys.lib+'/python',
          'include': '{installed_base}/include/python',
          'platinclude': '{installed_base}/include/python',
@@ -131,10 +135,11 @@ Index: Python-3.5.4/Lib/sysconfig.py
      'posix_user': {
 -        'stdlib': '{userbase}/lib/python{py_version_short}',
 -        'platstdlib': '{userbase}/lib/python{py_version_short}',
+-        'purelib': '{userbase}/lib/python{py_version_short}/site-packages',
+-        'platlib': '{userbase}/lib/python{py_version_short}/site-packages',
 +        'stdlib': '{userbase}/'+sys.lib+'/python{py_version_short}',
 +        'platstdlib': '{userbase}/'+sys.lib+'/python{py_version_short}',
-         'purelib': '{userbase}/lib/python{py_version_short}/site-packages',
--        'platlib': '{userbase}/lib/python{py_version_short}/site-packages',
++        'purelib': '{userbase}/'+sys.lib+'/python{py_version_short}/site-packages',
 +        'platlib': '{userbase}/'+sys.lib+'/python{py_version_short}/site-packages',
          'include': '{userbase}/include/python{py_version_short}',
          'scripts': '{userbase}/bin',
-- 
2.7.4

Re: [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

I thought that boost_python was the py2 binary, and boost_python3 was the
py3 one?  Is this not a bug in caffe?

On 13 March 2018 at 03:08, Jason Wessel <jason.wessel@windriver.com> wrote:

> When using an image built with the Yocto Project which has a compiler
> and all the required libraries, projects such as caffe for the
> Movidius SDK which use python3 and boost fail to build because they
> look for libboost_python.so.  The error that cmake returns doesn't
> even point to the fact that this is why the configuration fails.
>
> Example showing the problem with the missing symlink:
> ================
>   git clone https://github.com/weiliu89/caffe.git
>   cd caffe
>   mkdir build
>   cd build
>   cmake -DBLAS=Open ..
>
> -- Configuring done
> CMake Error at CMakeLists.txt:85 (add_dependencies):
>   The dependency target "pycaffe" of target "pytest" does not exist.
> ================
>
> Conditionally creating the link when building python3 support into
> boost is all that is needed.
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
>  meta/recipes-support/boost/boost.inc | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-support/boost/boost.inc
> b/meta/recipes-support/boost/boost.inc
> index 0461ec6..c53edf7 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -195,6 +195,9 @@ do_install() {
>                 fi
>         done
>
> +       if [ -e ${D}${libdir}/libboost_python3.so ]; then
> +               ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
> +       fi
>  }
>
>  BBCLASSEXTEND = "native nativesdk"
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2808 bytes --]

Re: [PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

This sounds very odd.  Can you give an example of this happening?

Ross

On 13 March 2018 at 03:08, Jason Wessel <jason.wessel@windriver.com> wrote:

> There are a number of other recipes outside oe-core that depend on
> alsa-lib and the rpm4 dependencies resolve sometimes to include
> alsa-lib and the packages in the other layers fail to install because
> the dependency cannot be resolved, despite the fact that libasound is
> installed.
>
> The simple is to add an RPROVIDES for alsa-lib to libasound which
> provides all the shared objects for alsa.
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
>  meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> index c5bf107..f7f01e8 100644
> --- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> +++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> @@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
>  FILES_alsa-conf = "${datadir}/alsa/"
>
>  RDEPENDS_libasound = "alsa-conf"
> +RPROVIDES_libasound = "alsa-lib"
>
>  # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
>  # alsa-lib package doesn't exist. libasound is the real library package.
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2678 bytes --]

Re: [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

[Jason Wessel]

[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]

Perhaps a bug in the cmake detect which is part of boost, because I am not using python2 for caffe.

I used the path of least resistance because as far as I could tell boost only let you build one or the other and in my case it was the python3 boost api. In the end caffe was working and all the python3 tests with the Movidius SDK pass (which use python3).

Jason.

On 03/14/2018 09:50 AM, Burton, Ross wrote:
> I thought that boost_python was the py2 binary, and boost_python3 was the py3 one?  Is this not a bug in caffe?
>
> On 13 March 2018 at 03:08, Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>> wrote:
>
>     When using an image built with the Yocto Project which has a compiler
>     and all the required libraries, projects such as caffe for the
>     Movidius SDK which use python3 and boost fail to build because they
>     look for libboost_python.so.  The error that cmake returns doesn't
>     even point to the fact that this is why the configuration fails.
>
>     Example showing the problem with the missing symlink:
>     ================
>       git clone https://github.com/weiliu89/caffe.git <https://github.com/weiliu89/caffe.git>
>       cd caffe
>       mkdir build
>       cd build
>       cmake -DBLAS=Open ..
>
>     -- Configuring done
>     CMake Error at CMakeLists.txt:85 (add_dependencies):
>       The dependency target "pycaffe" of target "pytest" does not exist.
>     ================
>
>     Conditionally creating the link when building python3 support into
>     boost is all that is needed.
>
>     Signed-off-by: Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>>
>     ---
>      meta/recipes-support/boost/boost.inc | 3 +++
>      1 file changed, 3 insertions(+)
>
>     diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
>     index 0461ec6..c53edf7 100644
>     --- a/meta/recipes-support/boost/boost.inc
>     +++ b/meta/recipes-support/boost/boost.inc
>     @@ -195,6 +195,9 @@ do_install() {
>                     fi
>             done
>
>     +       if [ -e ${D}${libdir}/libboost_python3.so ]; then
>     +               ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
>     +       fi
>      }
>
>      BBCLASSEXTEND = "native nativesdk"
>     --
>     2.7.4
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>


[-- Attachment #2: Type: text/html, Size: 4690 bytes --]

Re: [PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

[Jason Wessel]

[-- Attachment #1: Type: text/plain, Size: 2891 bytes --]


# dnf install python-pyalsaaudio
Last metadata expiration check: 0:00:44 ago on Wed Mar 14 11:15:23 2018.
Error:
  Problem: conflicting requests
   - nothing provides alsa-lib needed by python-pyalsaaudio-0.8.4-r0.1.core2_64

---
The python-pyalsaaudio recipe in question did the following:

DEPENDS += "alsa-lib"

RDEPENDS_${PN} += "\
         alsa-lib \
"

Obviously since nothing provides that, it isn't going to work. It is probably better in this case to change the python recipe to RDEPENDS on libasound which is what the alsa-lib recipe generates.  I can understand how the author of the python recipe might have been confused, but it begs the question of how it worked in the first place.  :-)

I can reach out to the owner of the layer that provided the recipe and you can drop this patch.

Jason.

On 03/14/2018 09:51 AM, Burton, Ross wrote:
> This sounds very odd.  Can you give an example of this happening?
>
> Ross
>
> On 13 March 2018 at 03:08, Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>> wrote:
>
>     There are a number of other recipes outside oe-core that depend on
>     alsa-lib and the rpm4 dependencies resolve sometimes to include
>     alsa-lib and the packages in the other layers fail to install because
>     the dependency cannot be resolved, despite the fact that libasound is
>     installed.
>
>     The simple is to add an RPROVIDES for alsa-lib to libasound which
>     provides all the shared objects for alsa.
>
>     Signed-off-by: Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>>
>     ---
>      meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb <http://alsa-lib_1.1.5.bb> | 1 +
>      1 file changed, 1 insertion(+)
>
>     diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb <http://alsa-lib_1.1.5.bb> b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb <http://alsa-lib_1.1.5.bb>
>     index c5bf107..f7f01e8 100644
>     --- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb <http://alsa-lib_1.1.5.bb>
>     +++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb <http://alsa-lib_1.1.5.bb>
>     @@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
>      FILES_alsa-conf = "${datadir}/alsa/"
>
>      RDEPENDS_libasound = "alsa-conf"
>     +RPROVIDES_libasound = "alsa-lib"
>
>      # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
>      # alsa-lib package doesn't exist. libasound is the real library package.
>     --
>     2.7.4
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>


[-- Attachment #2: Type: text/html, Size: 5283 bytes --]

Re: [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

[Jason Wessel]

[-- Attachment #1: Type: text/plain, Size: 3744 bytes --]


I can't seem to find where cmake's python checker magically decides the name of the shared object, but I did find an override, so you can drop the patch.   I had even gone so far as to simply make a zero length file instead of the symlink, and everything still built and run.  It is just some cmake detection which is broken.  The ubuntu/debian systems where this code is heavily tested all provide a link for the libboost_python.so which explains why this never turned up previously.  They don't get the option to pick python2 or python3 for boost, they always get both for now.

The override to build with python boost for cmake and caffe is as follows:

cmake -DBoost_PYTHON_LIBRARY_DEBUG=/usr/lib64/libboost_python3.so \
    -DBoost_PYTHON_LIBRARY_RELEASE=/usr/lib64/libboost_python3.so \
    -DBLAS=Open \
    ..


Cheers,
Jason.


On 03/14/2018 09:55 AM, Jason Wessel wrote:
> Perhaps a bug in the cmake detect which is part of boost, because I am not using python2 for caffe.
>
> I used the path of least resistance because as far as I could tell boost only let you build one or the other and in my case it was the python3 boost api. In the end caffe was working and all the python3 tests with the Movidius SDK pass (which use python3).
>
> Jason.
>
> On 03/14/2018 09:50 AM, Burton, Ross wrote:
>> I thought that boost_python was the py2 binary, and boost_python3 was the py3 one?  Is this not a bug in caffe?
>>
>> On 13 March 2018 at 03:08, Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>> wrote:
>>
>>     When using an image built with the Yocto Project which has a compiler
>>     and all the required libraries, projects such as caffe for the
>>     Movidius SDK which use python3 and boost fail to build because they
>>     look for libboost_python.so.  The error that cmake returns doesn't
>>     even point to the fact that this is why the configuration fails.
>>
>>     Example showing the problem with the missing symlink:
>>     ================
>>       git clone https://github.com/weiliu89/caffe.git <https://github.com/weiliu89/caffe.git>
>>       cd caffe
>>       mkdir build
>>       cd build
>>       cmake -DBLAS=Open ..
>>
>>     -- Configuring done
>>     CMake Error at CMakeLists.txt:85 (add_dependencies):
>>       The dependency target "pycaffe" of target "pytest" does not exist.
>>     ================
>>
>>     Conditionally creating the link when building python3 support into
>>     boost is all that is needed.
>>
>>     Signed-off-by: Jason Wessel <jason.wessel@windriver.com <mailto:jason.wessel@windriver.com>>
>>     ---
>>      meta/recipes-support/boost/boost.inc | 3 +++
>>      1 file changed, 3 insertions(+)
>>
>>     diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
>>     index 0461ec6..c53edf7 100644
>>     --- a/meta/recipes-support/boost/boost.inc
>>     +++ b/meta/recipes-support/boost/boost.inc
>>     @@ -195,6 +195,9 @@ do_install() {
>>                     fi
>>             done
>>
>>     +       if [ -e ${D}${libdir}/libboost_python3.so ]; then
>>     +               ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
>>     +       fi
>>      }
>>
>>      BBCLASSEXTEND = "native nativesdk"
>>     --
>>     2.7.4
>>
>>     --
>>     _______________________________________________
>>     Openembedded-core mailing list
>>     Openembedded-core@lists.openembedded.org <mailto:Openembedded-core@lists.openembedded.org>
>>     http://lists.openembedded.org/mailman/listinfo/openembedded-core <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>>
>>
>


[-- Attachment #2: Type: text/html, Size: 6284 bytes --]