[yocto] python tkinter dependencies
The python-tkinter module requires _tkinter. A result from a websearch suggested that I needed to make sure tk (from meta-oe/meta-oe) and tcl were installed before compiling python. I added a DEPENDS on the tk and tcl recipes to both python and python-tkinter in a python_2.7.3.bbappend. It did not work and was never built. I'm looking for tips to figure out what is going on. Thanks. - Jate S. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] regarding : [PATCH] libcap-ng: resolved issue related with LONG_BIT definition.
There was a patch posted on April 7th ( sorry don't have original email) From: "Alexandru.Vaduva" https://lists.yoctoproject.org/listinfo/yocto>> The problem is well known for 64 bits architectures and the solution is offered in the same recibe but in the meta-selinux layer. Signed-off-by: Alexandru.Vaduva https://lists.yoctoproject.org/listinfo/yocto>> --- recipes-security/libcap-ng/libcap-ng/python.patch | 39 + recipes-security/libcap-ng/libcap-ng_0.7.3.bb | 38 2 files changed, 71 insertions(+), 6 deletions(-) create mode 100644 recipes-security/libcap-ng/libcap-ng/python.patch I am seeing a build issue with meta-security that this patch fixes. was it Nack'd? regards, Armin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] adding libevent recipe
Hi, I am trying to add libevent to my current image. I added the line IMAGE_INSTALL_append = " libevent" in my local.conf with a path to meta in my bblayers .conf file, but when I load the image, I can't seem to find libevent. Would it be named something else? Am I missing some dependencies? I cannot seem to add any outside recipes to my core-image-sato and just wanted to try one, ie, libevent. I've tried other recipes with no success. Any help would be greatly appreciated. ~LC -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Understanding "Package groups"
Hi Stefan, You probably have found the explanation on package groups in the reference manual [1]. Package groups are recipes with the sole purpose to create dependencies to simplify image creation. A package group recipe bundles multiple packages together and then instead of having to explicitly specify each package in the IMAGE_INSTALL variable you can simply specify the package group name. Package group recipes look like this (from the manual): DESCRIPTION = "My Custom Package Groups" inherit packagegroup PACKAGES = "\ packagegroup-custom-apps \ packagegroup-custom-tools \ " RDEPENDS_packagegroup-custom-apps = "\ dropbear \ portmap \ psplash" RDEPENDS_packagegroup-custom-tools = "\ oprofile \ oprofileui-server \ lttng-control \ lttng-viewer" RRECOMMENDS_packagegroup-custom-tools = "\ kernel-module-oprofile" Like any recipe they have a description. They inherit the packagegroup.bbclass. A package group recipe can define multiple package groups in the PACKAGES variable. For each package group listed in PACKAGES you will then need to specify the packages that actually go into them with conditional RDEPENDS_ variables. Package groups are only relevant for the YP build system. They do not create package grouping for the package manager that you are using for your target. However, if you select a package group from HOB then all of the packages specified in that group should be installed in your target's rootfs by YP. Rudi [1] http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks On Tue, Jul 1, 2014 at 10:05 AM, Stefan Hofmann wrote: > Hi, > > I made my first steps with yocto and everything worked fine so far. But > now I am struggling with "package groups". What I basically want, is a > image for a base system, which allows me to install additional packages > over the air with opkg. In my imagination package groups are something like > preselected packages, which need to be installed at once similar like it is > handled in Debian for X11-support for example. Is this right ? I have built > core-image-base for testing purposes and tried to figure out the > dependencies by using the Hob tool. It says that bash will be installed and > the group "base/shell" is responsible for that. However it is not > installed, only ash and I cannot find a package group > "package-group-base-shell" in the receipes. It does however exist in the > work directory. So now I am somewhat confused. > > Regards, > Stefan > > -- > > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] gnupg: use wildcard in name
There are two versions of gnupg so limit the wildcard to the 2.x series
Signed-off-by: Armin Kuster
---
recipes-support/gnupg/{gnupg_2.0.22.bbappend => gnupg_2.%.bbappend} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-support/gnupg/{gnupg_2.0.22.bbappend => gnupg_2.%.bbappend}
(100%)
diff --git a/recipes-support/gnupg/gnupg_2.0.22.bbappend
b/recipes-support/gnupg/gnupg_2.%.bbappend
similarity index 100%
rename from recipes-support/gnupg/gnupg_2.0.22.bbappend
rename to recipes-support/gnupg/gnupg_2.%.bbappend
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Understanding "Package groups"
Hi, I made my first steps with yocto and everything worked fine so far. But now I am struggling with "package groups". What I basically want, is a image for a base system, which allows me to install additional packages over the air with opkg. In my imagination package groups are something like preselected packages, which need to be installed at once similar like it is handled in Debian for X11-support for example. Is this right ? I have built core-image-base for testing purposes and tried to figure out the dependencies by using the Hob tool. It says that bash will be installed and the group "base/shell" is responsible for that. However it is not installed, only ash and I cannot find a package group "package-group-base-shell" in the receipes. It does however exist in the work directory. So now I am somewhat confused. Regards, Stefan -- smime.p7s Description: S/MIME Cryptographic Signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't add shared libraries into final image
Thanks Nicolas
You're right. Now if you don't know ...
> -Original Message-
> From: Nicolas Dechesne [mailto:nicolas.deche...@linaro.org]
> Sent: mardi 1 juillet 2014 17:47
> To: Pierre Yves MORDRET
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Can't add shared libraries into final image
>
> On Tue, Jul 1, 2014 at 5:24 PM, Pierre Yves MORDRET yves.mord...@st.com> wrote:
> > I'm in front of an issue that I really don't understand. I wrote a quite
> > simple
> recipe to integrate an RPM package.
> > At the end of compilation/install/packaging/rootfs, I saw my shared
> libraries were not part of the final image.
> > I understood quickly after checking FILES_${PN}-dev. Since my shared
> libraries are .so (and not .so.X) , all of them fall into -dev package.
> >
> > Thus I naively add FILES_${PN} + =" ${libdir}/lib*.so " into my recipe ...
> > I was
> sure this would solve my issue, but don't .
> > Instead my shared libraries still remain in -dev package.
> >
> > Does anyone can't tell me why ? or point me out my mistake ?
>
> The -dev package is processed first during the packaging, so even though you
> try to add the .so in the main package, the files will be packaged in -dev
> first.
> you need to make sure that the .so are not pulled into the -dev package:
>
> FILES_SOLIBSDEV = ""
> FILES_${PN} += "${libdir}/*.so"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't add shared libraries into final image
On Tue, Jul 1, 2014 at 5:24 PM, Pierre Yves MORDRET
wrote:
> I'm in front of an issue that I really don't understand. I wrote a quite
> simple recipe to integrate an RPM package.
> At the end of compilation/install/packaging/rootfs, I saw my shared libraries
> were not part of the final image.
> I understood quickly after checking FILES_${PN}-dev. Since my shared
> libraries are .so (and not .so.X) , all of them fall into -dev package.
>
> Thus I naively add FILES_${PN} + =" ${libdir}/lib*.so " into my recipe ... I
> was sure this would solve my issue, but don't .
> Instead my shared libraries still remain in -dev package.
>
> Does anyone can't tell me why ? or point me out my mistake ?
The -dev package is processed first during the packaging, so even
though you try to add the .so in the main package, the files will be
packaged in -dev first. you need to make sure that the .so are not
pulled into the -dev package:
FILES_SOLIBSDEV = ""
FILES_${PN} += "${libdir}/*.so"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Can't add shared libraries into final image
Hello guys,
I'm in front of an issue that I really don't understand. I wrote a quite simple
recipe to integrate an RPM package.
At the end of compilation/install/packaging/rootfs, I saw my shared libraries
were not part of the final image.
I understood quickly after checking FILES_${PN}-dev. Since my shared libraries
are .so (and not .so.X) , all of them fall into -dev package.
Thus I naively add FILES_${PN} + =" ${libdir}/lib*.so " into my recipe ... I
was sure this would solve my issue, but don't .
Instead my shared libraries still remain in -dev package.
Does anyone can't tell me why ? or point me out my mistake ?
Thanks in advance.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] nscd: missing configuration and initscript
Hello folks, currently I'm trying to add nscd to my image. This works quite fine using IMAGE_INSTALL += "nscd". The problem is that the nscd package lacks a configuration and a initscript. I've searched through the recipes and the web but I can't find any hints on it. Is there a way to add a "complete nscd" installation (with config & initscript) without writing my own recipe? What is the preferred way for this? Am I overlooking something? thanks & regards, richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
