Re: [oe] [yocto] Bug in Open CV receipt
On Thu, Jul 23, 2015 at 11:30 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Thu, Jul 23, 2015 at 12:05 PM, Victor Rodriguez vm.ro...@gmail.com wrote: On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote: Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) You should add the dev-pkgs and tools-sdk image features for the image, not mangle it manually. I think the best solution is create a package group that will keep backward compatibility and aloud packages exist as expected Sorry but this does not make sense. The image recipe you described is not using the framework structure for this and this is the problem you should address not bloat the oe-core itself. Check core-image class for it. Thanks a lot for the help and answer these mails I will create a RFC patch just for this recipe and see what happen The problem is that when I add opencv to the image nothing is added not even the capabilities to run a binary with this library nor the capability to do development I will send the patch to the open embedded and see what the community think Best regards Victor Rodriguez -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Question about IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL
On Sat, Jul 25, 2015 at 7:26 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-07-24 18:37, Khem Raj wrote: On Tue, Jul 21, 2015 at 8:36 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-07-21 09:26, Victor Rodriguez wrote: Hi team I have a question , according to documentation there is a difference between IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL Specifies the list of packages to be added to the image. You should only set this variable in the local.conf configuration file found in the Build Directory. When I use the second one and try to build a core-image-minimal-xfce bitbake does not install what I wanted in my image . I had a really hard time few weekends ago because of this. I wonder If I am missing something or if this is a bug The core-image-minimal-xfce recipe does not play nice with the core-image class and is not respecting CORE_IMAGE_EXTRA_INSTALL. its not required to. Maybe it's not required, but since that is the recommended way to add packages to an image, it probably should. As you can see from the original question, the non-standard behaviour is confusing, certainly to new users. It would only take a little reorganization to make it work as expected. I really apreciate all the time you take to answer this mail I would like to summarize this part and came to a final conclusion Should I try to fix or should we leave it as it is ? Best regards Victor Rodriguez I think this should be filed as a bug (and feel free to suggest a patch) No. Its not OE-Core or yocto bug BTW, this question should really be on the OpenEmbedded development list. its valid for meta-xfce only. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Question about IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL
On Wed, Jul 22, 2015 at 8:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 21 July 2015 14:51:55 Victor Rodriguez wrote: On Tue, Jul 21, 2015 at 12:41 PM, Leonardo Sandoval leonardo.sandoval.gonza...@linux.intel.com wrote: On 07/21/2015 10:45 AM, Victor Rodriguez wrote: On Tue, Jul 21, 2015 at 10:36 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-07-21 09:26, Victor Rodriguez wrote: Hi team I have a question , according to documentation there is a difference between IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL Specifies the list of packages to be added to the image. You should only set this variable in the local.conf configuration file found in the Build Directory. When I use the second one and try to build a core-image-minimal-xfce bitbake does not install what I wanted in my image . I had a really hard time few weekends ago because of this. I wonder If I am missing something or if this is a bug The core-image-minimal-xfce recipe does not play nice with the core-image class and is not respecting CORE_IMAGE_EXTRA_INSTALL. I think this should be filed as a bug (and feel free to suggest a patch) BTW, this question should really be on the OpenEmbedded development list. Thanks Gary I will submit the BUG , do you know the Bugzila where I should submit it ? Victor, you can file a bug at https://bugzilla.yoctoproject.org I think we have one already https://bugzilla.yoctoproject.org/show_bug.cgi?id=7616 That's not the right bug. If the suggestion is that core-image-minimal-xfce needs to be fixed, that's not a bug we would track in the Yocto Project bugzilla (since the Yocto Project is not actively involved in maintaining meta-xfce). Cheers, Paul Hi Paul Where can I track this ? -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Bug in Open CV receipt
On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote: Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) You should add the dev-pkgs and tools-sdk image features for the image, not mangle it manually. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ yocto mailing list yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto I think the best solution is create a package group that will keep backward compatibility and aloud packages exist as expected -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Bug in Open CV receipt
Hi team Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) Hope it helps to cut the time of some others Best regards Victor Rodriguez -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Question about IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL
On Tue, Jul 21, 2015 at 10:36 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-07-21 09:26, Victor Rodriguez wrote: Hi team I have a question , according to documentation there is a difference between IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL Specifies the list of packages to be added to the image. You should only set this variable in the local.conf configuration file found in the Build Directory. When I use the second one and try to build a core-image-minimal-xfce bitbake does not install what I wanted in my image . I had a really hard time few weekends ago because of this. I wonder If I am missing something or if this is a bug The core-image-minimal-xfce recipe does not play nice with the core-image class and is not respecting CORE_IMAGE_EXTRA_INSTALL. I think this should be filed as a bug (and feel free to suggest a patch) BTW, this question should really be on the OpenEmbedded development list. Thanks Gary I will submit the BUG , do you know the Bugzila where I should submit it ? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Question about IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL
On Tue, Jul 21, 2015 at 12:41 PM, Leonardo Sandoval leonardo.sandoval.gonza...@linux.intel.com wrote: On 07/21/2015 10:45 AM, Victor Rodriguez wrote: On Tue, Jul 21, 2015 at 10:36 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-07-21 09:26, Victor Rodriguez wrote: Hi team I have a question , according to documentation there is a difference between IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL Specifies the list of packages to be added to the image. You should only set this variable in the local.conf configuration file found in the Build Directory. When I use the second one and try to build a core-image-minimal-xfce bitbake does not install what I wanted in my image . I had a really hard time few weekends ago because of this. I wonder If I am missing something or if this is a bug The core-image-minimal-xfce recipe does not play nice with the core-image class and is not respecting CORE_IMAGE_EXTRA_INSTALL. I think this should be filed as a bug (and feel free to suggest a patch) BTW, this question should really be on the OpenEmbedded development list. Thanks Gary I will submit the BUG , do you know the Bugzila where I should submit it ? Victor, you can file a bug at https://bugzilla.yoctoproject.org I think we have one already https://bugzilla.yoctoproject.org/show_bug.cgi?id=7616 -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Bug in Open CV receipt
On Tue, Jul 21, 2015 at 3:49 PM, Leonardo Sandoval leonardo.sandoval.gonza...@linux.intel.com wrote: On 07/21/2015 09:57 AM, Victor Rodriguez wrote: Hi team Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv A recipe can produce several packages. As I can see on opencv recipe, it can produced the following ones: PACKAGES=opencv-staticdev opencv-dev opencv-dbg opencv-doc opencv opencv-apps python-opencv and dynamic ones (depending on what else you have install) PACKAGES_DYNAMIC=^opencv-locale-.* ^libopencv-.* For the opencv case, it happens that the package opencv is empty, so you need to append the other sub-packages it produces into your IMAGE_INSTALL variable. So, it is not a bug, this is expected. In my humble opinion this should change for OpenCV. But I would love to hear the feedback from others Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) Hope it helps to cut the time of some others Best regards Victor Rodriguez -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] mpich: added BASH_SHELL to CACHED_CONFIGUREVARS
On Sun, May 10, 2015 at 1:27 AM, Victor Rodriguez
victor.rodriguez.bah...@intel.com wrote:
On Fedora 17, bash has moved to /usr/bin/bash and the configure process finds
it on the host machine there, this ensures that it is set correctly for the
target.
Signed-off-by: Victor Rodriguez victor.rodriguez.bah...@intel.com
---
meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
index 0225cee..eb6ceba 100644
--- a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
+++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
@@ -12,6 +12,8 @@ SRC_URI = \
SRC_URI[md5sum] = 40dc408b1e03cc36d80209baaa2d32b7
SRC_URI[sha256sum] =
455ccfaf4ec724d2cf5d8bff1f3d26a958ad196121e7ea26504fd3018757652d
+CACHED_CONFIGUREVARS += BASH_SHELL=${base_bindir}/bash
+
RDEPENDS_${PN} += bash perl libxml2
S = ${WORKDIR}/${PN}-${PV}
--
1.9.3
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Hi team .. this patch is important otherwise we can not create an
image with mpich in Fedora
If there is other way or is already fixed I am more than happy to know
to apply that
Thanks and regards
Victor Rodriguez
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH] mpich: added BASH_SHELL to CACHED_CONFIGUREVARS
On Fedora 17, bash has moved to /usr/bin/bash and the configure process finds
it on the host machine there, this ensures that it is set correctly for the
target.
Signed-off-by: Victor Rodriguez victor.rodriguez.bah...@intel.com
---
meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
index 0225cee..eb6ceba 100644
--- a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
+++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
@@ -12,6 +12,8 @@ SRC_URI = \
SRC_URI[md5sum] = 40dc408b1e03cc36d80209baaa2d32b7
SRC_URI[sha256sum] =
455ccfaf4ec724d2cf5d8bff1f3d26a958ad196121e7ea26504fd3018757652d
+CACHED_CONFIGUREVARS += BASH_SHELL=${base_bindir}/bash
+
RDEPENDS_${PN} += bash perl libxml2
S = ${WORKDIR}/${PN}-${PV}
--
1.9.3
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 2/2] mpich: Disable RPATH to avoid issues in package_qa
From: Aníbal Limón anibal.li...@linux.intel.com
Set --disable-rpath to extra opts in order to avoid issues
in package_qa also change default pm to gforker because
hydra has problems with RPATH.
TODO: Make a patch for solve hydra rpath issues.
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
index 2f4226e..0225cee 100644
--- a/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
+++ b/meta-oe/recipes-devtools/mpich/mpich_3.1.1.bb
@@ -1,20 +1,25 @@
-SUMMARY = Message Passing Interface(MPI) implementation
-HOMEPAGE = http://git.mpich.org/mpich.git/;
+SUMMARY = Message Passing Interface (MPI) implementation
+HOMEPAGE = http://www.mpich.org/;
SECTION = devel
LICENSE = BSD-2-Clause
LIC_FILES_CHKSUM = file://COPYRIGHT;md5=2106f0435056f3dd9349747a766e5816
-SRC_URI = http://www.mpich.org/static/downloads/${PV}/mpich-${PV}.tar.gz;
+SRC_URI = \
+ http://www.mpich.org/static/downloads/${PV}/mpich-${PV}.tar.gz \
+
+
SRC_URI[md5sum] = 40dc408b1e03cc36d80209baaa2d32b7
SRC_URI[sha256sum] =
455ccfaf4ec724d2cf5d8bff1f3d26a958ad196121e7ea26504fd3018757652d
-RDEPENDS_${PN} += bash perl tcsh
+RDEPENDS_${PN} += bash perl libxml2
S = ${WORKDIR}/${PN}-${PV}
EXTRA_OECONF = --enable-debuginfo \
--enable-fast \
--enable-shared \
+--with-pm=gforker \
+ --disable-rpath \
--disable-f77 \
--disable-fc \
--disable-fortran \
--
1.9.3
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
