[yocto] Is there anything like FILES_${PN}_append??

[Amit Tomer]

I have made some changes in .bb file related to openssh but this openssh
package is shared among variuos platforms and I want these changes to
be reflected
only to specific platform.

Now for variable SRC_URI ,I can do something like SRC_URI_append_xyz where
xyz is my platform where changes should be reflected.

Now there is one more Variable I added is FILES_${PN ,Now I wanted this variable
also to be xyz specific

So is there anything  like FILES_${PN}_append exist in yocto.

Or what other way to make it platform specific.

Thanks
Amit
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] clarification on what packages are *truly* needed for a yocto build?

[Robert P. J. Day]

  (aside: prepping to teach an OE/yocto course in a couple weeks,
going thru the docs again, so be prepared for questions, some of them
potentially silly but all in aid of clarifying bits of documentation.
i'm sure scott rifenbark is currently steeling himself for the
experience. :-)

  i'm intimately aware of the current doc pages that list how to
establish your yocto build environment, such as this:

https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies

but a question or two.

  in some cases, i've seen, say, subversion listed as a prerequisite,
even though subversion is clearly built natively. so is it *truly* a
user-installable prerequisite? or am i misreading something?

  also, at this point, is there a list of what one can safely add to
ASSUME_PROVIDED to cut down build time on a new project? i recall from
way back when that, if you use ASSUME_PROVIDED, you're sort of voiding
the warranty in terms of what's been quality checked. but if one is
willing to take a chance, is there a set of packages that would be
considered "safe" to assume are provided? (for example, i would assume
that, in any current distro, git would certainly be safe, no?)

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] clarification on what packages are *truly* needed for a yocto build?

[Paul Eggleton]

Hi Robert,

On Wednesday 09 October 2013 06:45:36 Robert P. J. Day wrote:
>   (aside: prepping to teach an OE/yocto course in a couple weeks,
> going thru the docs again, so be prepared for questions, some of them
> potentially silly but all in aid of clarifying bits of documentation.
> i'm sure scott rifenbark is currently steeling himself for the
> experience. :-)
> 
>   i'm intimately aware of the current doc pages that list how to
> establish your yocto build environment, such as this:
> 
> https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies

That page is very much unmaintained and out-of-date. We should probably note
as much on the page (or just delete it). The canonical list of build host
dependencies can always be found in the Quick Start guide:

http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html

(substitute "current" in that URL with "1.5" if you'll be training with the
1.5 release, until the release happens at which point those will be the same
thing).

> but a question or two.
> 
>   in some cases, i've seen, say, subversion listed as a prerequisite,
> even though subversion is clearly built natively. so is it *truly* a
> user-installable prerequisite? or am i misreading something?

No, subversion is not needed on the host. git is however (and specifically for
the 1.5 release onwards, git 1.7.5 or later is required.)

>   also, at this point, is there a list of what one can safely add to
> ASSUME_PROVIDED to cut down build time on a new project? i recall from
> way back when that, if you use ASSUME_PROVIDED, you're sort of voiding
> the warranty in terms of what's been quality checked. but if one is
> willing to take a chance, is there a set of packages that would be
> considered "safe" to assume are provided? (for example, i would assume
> that, in any current distro, git would certainly be safe, no?)

When we say you're on your own setting this, you really are on your own ;)
We do not QA setting this variable differently from the default, and so it's a
bit hard for us to make any guarantees that any particular value that differs
from the default will be "safe". (FWIW, in dylan/1.4 and later, git-native is
already in the default value of ASSUME_PROVIDED).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 0/5] Remove python dependency from refpol.

[Joe MacDonald]

[[meta-selinux][PATCH 0/5] Remove python dependency from refpol.] On 13.10.09 
(Wed 03:02) fl...@longhaul.twobit.us wrote:

> The reference policy package currently pulls in a lot of python stuff
> that isn't strictly necessary to boot an SELinux system and load a
> policy. This is caused by the mix of python and C utilities in
> policycoreutils.
> 
> This patch set breaks the policycoreutils recipe up into multiple
> packages, one for each utility. In this way we can have the refpol etc
> pull in only the utilities necessary for normal operation. This happens
> to be only the utilities written in C and thus we can remove python
> completely in a minimal image.
> 
> I've attempted to localize these changes as much as possible so changes
> in this patchset outside of the policycoreutils recipe are few. An
> example image reicpe is added to demonstrate a minimal image with only
> the utilities required to load a policy and manipulate the policy store
> (add / remove policy modules) at runtime.

Hey Philip,

The patches never arrived in my mailbox and I don't see them in
patchworks.  Can you re-send, please?

-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH 0/5] Remove python dependency from refpol.

[Philip Tricca]

The reference policy package currently pulls in a lot of python stuff
that isn't strictly necessary to boot an SELinux system and load a
policy. AFAIK this is caused by the mix of python and C utilities in
policycoreutils.

This patch set breaks the policycoreutils recipe up into multiple
packages, one for each utility. In this way we can have the refpol etc
pull in only the utilities necessary for normal operation. This happens
to be only the utilities written in C and thus we can remove python
completely in a minimal image.

I've attempted to localize these changes as much as possible so this
patch set should have minimal impact on recipes outside of the
policycoreutils. An example image reicpe is added to demonstrate a
minimal image with only the utilities required to load a policy and
manipulate the policy store (add / remove policy modules) at runtime.

Regards,
- Philip
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 0/5] Remove python dependency from refpol.

[Philip Tricca]

Morning Joe

On 10/09/2013 08:23 AM, Joe MacDonald wrote:
> [[meta-selinux][PATCH 0/5] Remove python dependency from refpol.]
> On 13.10.09 (Wed 03:02) fl...@longhaul.twobit.us wrote:
> 
>> The reference policy package currently pulls in a lot of python
>> stuff that isn't strictly necessary to boot an SELinux system and
>> load a policy. This is caused by the mix of python and C
>> utilities in policycoreutils.
>> 
>> This patch set breaks the policycoreutils recipe up into
>> multiple packages, one for each utility. In this way we can have
>> the refpol etc pull in only the utilities necessary for normal
>> operation. This happens to be only the utilities written in C and
>> thus we can remove python completely in a minimal image.
>> 
>> I've attempted to localize these changes as much as possible so
>> changes in this patchset outside of the policycoreutils recipe
>> are few. An example image reicpe is added to demonstrate a
>> minimal image with only the utilities required to load a policy
>> and manipulate the policy store (add / remove policy modules) at
>> runtime.
> 
> Hey Philip,
> 
> The patches never arrived in my mailbox and I don't see them in 
> patchworks.  Can you re-send, please?

I don't think this message made it to the list. Must have made it to
you and Mark though. I've resent and will send patches momentarily.

Cheers,
- Philip

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 1/5] Break policycoreutils out into separate packages for the various utilities.

[Philip Tricca]

The driver beind this is to allow images to be built with the minimal
tools necessary to load a policy.  Breaking all of the stuff that's
dependent on python out from the core utils allows us to make much
smaller images.

Signed-off-by: Philip Tricca 
---
 recipes-security/selinux/policycoreutils.inc |  181 +-
 1 file changed, 175 insertions(+), 6 deletions(-)

diff --git a/recipes-security/selinux/policycoreutils.inc 
b/recipes-security/selinux/policycoreutils.inc
index dfd65e3..e6ff4ed 100644
--- a/recipes-security/selinux/policycoreutils.inc
+++ b/recipes-security/selinux/policycoreutils.inc
@@ -38,6 +38,92 @@ RDEPENDS_${BPN} += "\
python-ipy \
"
 
+RDEPENDS_${BPN}-audit2allow = " \
+   python-textutils \
+   libselinux-python \
+   sepolgen \
+   "
+RDEPENDS_${BPN}-chcat = " \
+   python-codecs \
+   python-shell \
+   python-stringold \
+   python-unixadmin \
+   ${BPN}-python \
+   libselinux-python \
+   "
+RDEPENDS_${BPN}-fixfiles += "\
+   ${BPN}-setfiles \
+   "
+RDEPENDS_${BPN}-genhomedircon += "\
+   ${BPN}-genhomedircon \
+   ${BPN}-semodule \
+   "
+RDEPENDS_${BPN}-loadpolicy += "\
+   libselinux \
+   libsepol \
+   "
+RDEPENDS_${BPN}-newrole += "\
+   libcap-ng \
+   libselinux \
+   "
+RDEPENDS_${BPN}-python += "\
+   python-codecs \
+   python-io \
+   python-ipy \
+   python-re \
+   python-stringold \
+   python-syslog \
+   python-unixadmin \
+   libselinux-python \
+   libsemanage-python \
+   "
+RDEPENDS_${BPN}-runinit += "libselinux"
+RDEPENDS_${BPN}-sandbox += "\
+   python-math \
+   python-shell \
+   python-subprocess \
+   python-textutils \
+   python-unixadmin \
+   libselinux-python \
+   ${BPN}-python \
+   "
+RDEPENDS_${BPN}-secon += "libselinux"
+RDEPENDS_${BPN}-semanage = " \
+   python-core \
+   python-ipy \
+   ${BPN}-python \
+   libselinux-python \
+   "
+RDEPENDS_${BPN}-semodule += "\
+   libsepol \
+   libselinux \
+   libsemanage \
+   "
+# static link to libsepol
+DEPENDS_${BPN}-semodule-deps += "libsepol"
+RDEPENDS_${BPN}-semodule-expand += "libsepol libselinux"
+RDEPENDS_${BPN}-semodule-link += "libsepol libselinux"
+RDEPENDS_${BPN}-semodule-package += "libsepol libselinux"
+RDEPENDS_${BPN}-sepolicy += "\
+   python-argparse \
+   python-codecs \
+   python-core \
+   python-syslog \
+   ${BPN}-python \
+   "
+# static link to libsepol
+DEPENDS_${BPN}-sepolgen-ifgen += "libsepol"
+RDEPENDS_${BPN}-sepolgen-ifgen += "libselinux-python"
+RDEPENDS_${BPN}-sestatus += "libselinux"
+RDEPENDS_${BPN}-setfiles += "\
+   libselinux \
+   libsepol \
+   "
+RDEPENDS_${BPN}-setsebool += "\
+   libsepol \
+   libselinux \
+   libsemanage \
+   "
 RDEPENDS_${BPN} += "setools setools-libs ${BPN}-python"
 
 WARN_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${WARN_QA}', d)}"
@@ -45,14 +131,97 @@ ERROR_QA := 
"${@oe_filter_out('unsafe-references-in-scripts', '${ERROR_QA}', d)}
 
 inherit pythonnative
 
-PACKAGES =+ "${PN}-python ${PN}-sandbox system-config-selinux"
-FILES_${PN}-python = 
"${libdir}/python${PYTHON_BASEVERSION}/site-packages/seobject.py* \
+PACKAGES =+ "\
+   ${PN}-audit2allow \
+   ${PN}-chcat \
+   ${PN}-fixfiles \
+   ${PN}-genhomedircon \
+   ${PN}-loadpolicy \
+   ${PN}-newrole \
+   ${PN}-python \
+   ${PN}-runinit \
+   ${PN}-sandbox \
+   ${PN}-secon \
+   ${PN}-semanage \
+   ${PN}-semodule \
+   ${PN}-semodule-deps \
+   ${PN}-semodule-expand \
+   ${PN}-semodule-link \
+   ${PN}-semodule-package \
+   ${PN}-sepolgen-ifgen \
+   ${PN}-sepolicy \
+   ${PN}-sestatus \
+   ${PN}-setfiles \
+   ${PN}-setsebool \
+   system-config-selinux \
+   "
+FILES_${PN}-audit2allow = " \
+   ${bindir}/audit2allow \
+   ${bindir}/audit2why \
+   "
+FILES_${PN}-chcat = " \
+   ${bindir}/chcat \
+   "
+FILES_${PN}-fixfiles += "${base_sbindir}/fixfiles"
+FILES_${PN}-genhomedircon += "${sbindir}/genhomedircon"
+FILES_${PN}-loadpolicy += "\
+   ${base_sbindir}/load_policy \
+   ${sbindir}/load_policy \
+   "
+FILES_${PN}-newrole += "\
+   ${bindir}/newrole \
+   ${@base_contains('DISTRO_FEATURES', 'pam', 
'${sysconfdir}/pam.d/newrole', '', d)} \
+   "
+FILES_${PN}-python = " \
+   ${libdir}/python${PYTHON_BASEVERSION}/site-packages/seobject.py* \
${libdir}/python${PYTHON_BASEVERSION}/site-packages/sepolicy*.egg-info \
-   ${libdir}/python${PYTHON_BASEVERSION}/site-packages/sepolicy/*"
+   ${libdir}/python${PYTHON_BASEVERSION}/site-packages/sepolicy/* \
+"
+FILES_${PN}-runinit += "\
+   ${sbindir}/run_init \
+   ${sbindir}/open_init_pty \
+   ${@base_contains('DISTRO_FEATURES', 'pam', 
'${sysconfdir}/pam.d/run_

Re: [yocto] TtyUsb Yocto Issue

[Jawad Hassan]

Hi Paul,

Thanks for your reply, but we're not seeing any ttyUSB* entries in the /dev
folder, the board is this one here:
http://boundarydevices.com/products/nitrogen6_lite/

Which should have at least one port available for connection.

But unfortunately we aren't seeing this device node. What should be our way
forward with this?

Thanks in advance!


On Tue, Oct 8, 2013 at 9:04 AM, Paul Eggleton  wrote:

> Hi Jawad,
>
> On Tuesday 08 October 2013 06:43:18 Jawad Hassan wrote:
> > We're trying to access the USB serial port using rxtx on a java
> application
> > on Yocto. The problem is that we're unable to list out any ports on the
> > Nitrogen Lite board, we think this could be a permissions issue, if
> anyone
> > has been able to do this or any resources that can help us in getting
> this
> > done.
>
> It's hard to say for sure without further details, but assuming the device
> nodes actually exist in /dev and it's a typical device permissions issue
> there
> are two options:
>
> 1) Look at the /dev/ttyUSB* device nodes that exist and see if there is
> already a group assigned with write access; if so you just need to ensure
> the
> user you are running as is a member of that group.
>
> 2) Create a udev rule to set the device permissions correctly. This would
> be a
> matter of creating a recipe to install an extra file to /etc/udev/rules.d
> that
> assigned the desired permissions. There are lots of HOWTOs out there on the
> web for this, e.g.:
>
>
> http://sourceforge.net/apps/mediawiki/gizmod/index.php?title=HOWTO_-_Setting_Input_Device_Permissions_-_Creating_a_udev_Rule
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>



-- 
*Jawad Hassan*
Software Engineer
*Emblem Technologies (Pvt) Ltd*
*Uzair Pte Ltd, Singapore*
Skype: ja...@emblemtechnologies.com

LinkedIn  |
Twitter
 | Facebook 

*This message contains confidential information and is intended only for
the individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. Email transmission cannot be guaranteed to be
secure or error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late, incomplete, or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which may arise as a result of email transmission.
If verification is required, please request a hard-copy version.*
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 2/5] Remove unnecessary RDEPENDS_${BPN}.

[Philip Tricca]

Now that the policycoreutuils package is empty no need for RDEPENDS.
Doing this in the commit that broke up the policycoreutuils package
made the diff hard to read. Figured it best to break it out for
readability.

Signed-off-by: Philip Tricca 
---
 recipes-security/selinux/policycoreutils.inc |   16 
 1 file changed, 16 deletions(-)

diff --git a/recipes-security/selinux/policycoreutils.inc 
b/recipes-security/selinux/policycoreutils.inc
index e6ff4ed..05de7ac 100644
--- a/recipes-security/selinux/policycoreutils.inc
+++ b/recipes-security/selinux/policycoreutils.inc
@@ -22,22 +22,6 @@ DEPENDS += "${@['', '${EXTRA_DEPENDS}']['${PN}' != 
'${BPN}-native']}"
 inherit selinux
 DEPENDS += "${@target_selinux(d, 'libpam audit')}"
 
-RDEPENDS_${BPN} += "\
-   libselinux-python \
-   libsemanage-python \
-   sepolgen \
-   "
-RDEPENDS_${BPN} += "\
-   python \
-   python-unixadmin \
-   python-shell \
-   python-crypt \
-   python-subprocess \
-   python-syslog \
-   python-textutils \
-   python-ipy \
-   "
-
 RDEPENDS_${BPN}-audit2allow = " \
python-textutils \
libselinux-python \
-- 
1.7.10.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 3/5] Remove runtime dependency on policycoreutils from the reference policy.

[Philip Tricca]

The only thing refpol needs to depend on at runtime are the things
necessary to load the policy.  If sysvinit is patched to load the
policy (which it is) then we only need the config.

Signed-off-by: Philip Tricca 
---
 recipes-security/refpolicy/refpolicy_common.inc |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/refpolicy/refpolicy_common.inc 
b/recipes-security/refpolicy/refpolicy_common.inc
index 3eaf16d..873d887 100644
--- a/recipes-security/refpolicy/refpolicy_common.inc
+++ b/recipes-security/refpolicy/refpolicy_common.inc
@@ -16,7 +16,7 @@ FILES_${PN} = "${sysconfdir}/selinux/${POLICY_NAME}/ \
 FILES_${PN}-dev =+ "${datadir}/selinux/${POLICY_NAME}/include/"
 
 DEPENDS += "checkpolicy-native policycoreutils-native m4-native"
-RDEPENDS_${PN} += "policycoreutils selinux-config"
+RDEPENDS_${PN} += "selinux-config"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
-- 
1.7.10.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 4/5] Add packagegroup and image recipe for minimal SELinux image.

[Philip Tricca]

This is intended to demonstrate the minimal set packages necessary
to boot and load a system with SELinux enabled. Specifically we
don't need any of the packages that depend on python.

Signed-off-by: Philip Tricca 
---
 .../images/core-image-selinux-minimal.bb   |   15 +++
 .../packagegroups/packagegroup-selinux-minimal.bb  |   26 
 2 files changed, 41 insertions(+)
 create mode 100644 recipes-security/images/core-image-selinux-minimal.bb
 create mode 100644 
recipes-security/packagegroups/packagegroup-selinux-minimal.bb

diff --git a/recipes-security/images/core-image-selinux-minimal.bb 
b/recipes-security/images/core-image-selinux-minimal.bb
new file mode 100644
index 000..45cd847
--- /dev/null
+++ b/recipes-security/images/core-image-selinux-minimal.bb
@@ -0,0 +1,15 @@
+DESCRIPTION = "Minimal image with SELinux support (no python)"
+
+IMAGE_FEATURES += "splash ssh-server-openssh"
+
+LICENSE = "MIT"
+
+IMAGE_INSTALL = "\
+   ${CORE_IMAGE_BASE_INSTALL} \
+   bash \
+   util-linux-agetty \
+   packagegroup-core-boot \
+   packagegroup-selinux-minimal \
+"
+
+inherit core-image
diff --git a/recipes-security/packagegroups/packagegroup-selinux-minimal.bb 
b/recipes-security/packagegroups/packagegroup-selinux-minimal.bb
new file mode 100644
index 000..16f6bae
--- /dev/null
+++ b/recipes-security/packagegroups/packagegroup-selinux-minimal.bb
@@ -0,0 +1,26 @@
+DESCRIPTION = "SELinux packagegroup with only packages required for basic 
operations"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
+
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PR = "r0"
+
+PACKAGES = "\
+   ${PN} \
+   "
+
+ALLOW_EMPTY_${PN} = "1"
+
+RDEPENDS_${PN} = " \
+   coreutils \
+   libsepol \
+   libselinux \
+   libselinux-bin \
+   libsemanage \
+   policycoreutils-fixfiles \
+   policycoreutils-secon \
+   policycoreutils-semodule \
+   policycoreutils-sestatus \
+   policycoreutils-setfiles \
+   selinux-config \
+   refpolicy-mls \
+   "
-- 
1.7.10.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 5/5] Add packagegroup for policycoreutils packages.

[Philip Tricca]

The policycoreutils package previously included most everything in
the base package. This packagegroup is intended to fill the role
of the old policycoreutils package and pull in all packages from the
policycoreutils recipe.

Signed-off-by: Philip Tricca 
---
 .../packagegroups/packagegroup-core-selinux.bb |4 +--
 .../packagegroup-selinux-policycoreutils.bb|   36 
 2 files changed, 37 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-security/packagegroups/packagegroup-selinux-policycoreutils.bb

diff --git a/recipes-security/packagegroups/packagegroup-core-selinux.bb 
b/recipes-security/packagegroups/packagegroup-core-selinux.bb
index 7cd7409..76863b0 100644
--- a/recipes-security/packagegroups/packagegroup-core-selinux.bb
+++ b/recipes-security/packagegroups/packagegroup-core-selinux.bb
@@ -19,9 +19,7 @@ RDEPENDS_${PN} = " \
libsemanage \
checkpolicy \
sepolgen \
-   policycoreutils \
-   policycoreutils-sandbox \
-   policycoreutils-python \
+   packagegroup-selinux-policycoreutils \
setools \
setools-console \
selinux-config \
diff --git 
a/recipes-security/packagegroups/packagegroup-selinux-policycoreutils.bb 
b/recipes-security/packagegroups/packagegroup-selinux-policycoreutils.bb
new file mode 100644
index 000..296a7e3
--- /dev/null
+++ b/recipes-security/packagegroups/packagegroup-selinux-policycoreutils.bb
@@ -0,0 +1,36 @@
+DESCRIPTION = "SELinux policycoreutils packagegroup"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
+
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PR = "r0"
+
+PACKAGES = "\
+${PN} \
+"
+
+ALLOW_EMPTY_${PN} = "1"
+
+RDEPENDS_${PN} = " \
+   policycoreutils-audit2allow \
+   policycoreutils-chcat \
+   policycoreutils-fixfiles \
+   policycoreutils-genhomedircon \
+   policycoreutils-loadpolicy \
+   policycoreutils-newrole \
+   policycoreutils-python \
+   policycoreutils-runinit \
+   policycoreutils-sandbox \
+   policycoreutils-secon \
+   policycoreutils-semanage \
+   policycoreutils-semodule \
+   policycoreutils-semodule-deps \
+   policycoreutils-semodule-expand \
+   policycoreutils-semodule-link \
+   policycoreutils-semodule-package \
+   policycoreutils-sepolgen-ifgen \
+   policycoreutils-sepolicy \
+   policycoreutils-sestatus \
+   policycoreutils-setfiles \
+   policycoreutils-setsebool \
+   system-config-selinux \
+   "
-- 
1.7.10.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] TtyUsb Yocto Issue

[Jawad Hassan]

PS. /etc/device_list does show a ttyUSB entry


On Wed, Oct 9, 2013 at 5:36 AM, Jawad Hassan
wrote:

> Hi Paul,
>
> Thanks for your reply, but we're not seeing any ttyUSB* entries in the
> /dev folder, the board is this one here:
> http://boundarydevices.com/products/nitrogen6_lite/
>
> Which should have at least one port available for connection.
>
> But unfortunately we aren't seeing this device node. What should be our
> way forward with this?
>
> Thanks in advance!
>
>
> On Tue, Oct 8, 2013 at 9:04 AM, Paul Eggleton <
> paul.eggle...@linux.intel.com> wrote:
>
>> Hi Jawad,
>>
>> On Tuesday 08 October 2013 06:43:18 Jawad Hassan wrote:
>> > We're trying to access the USB serial port using rxtx on a java
>> application
>> > on Yocto. The problem is that we're unable to list out any ports on the
>> > Nitrogen Lite board, we think this could be a permissions issue, if
>> anyone
>> > has been able to do this or any resources that can help us in getting
>> this
>> > done.
>>
>> It's hard to say for sure without further details, but assuming the device
>> nodes actually exist in /dev and it's a typical device permissions issue
>> there
>> are two options:
>>
>> 1) Look at the /dev/ttyUSB* device nodes that exist and see if there is
>> already a group assigned with write access; if so you just need to ensure
>> the
>> user you are running as is a member of that group.
>>
>> 2) Create a udev rule to set the device permissions correctly. This would
>> be a
>> matter of creating a recipe to install an extra file to /etc/udev/rules.d
>> that
>> assigned the desired permissions. There are lots of HOWTOs out there on
>> the
>> web for this, e.g.:
>>
>>
>> http://sourceforge.net/apps/mediawiki/gizmod/index.php?title=HOWTO_-_Setting_Input_Device_Permissions_-_Creating_a_udev_Rule
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>>
>
>
>
> --
> *Jawad Hassan*
> Software Engineer
> *Emblem Technologies (Pvt) Ltd*
> *Uzair Pte Ltd, Singapore*
> Skype: ja...@emblemtechnologies.com
>
> LinkedIn  | 
> Twitter
>  | Facebook 
>
> *This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee, you should not
> disseminate, distribute or copy this email. Please notify the sender
> immediately by email if you have received this email by mistake and delete
> this email from your system. Email transmission cannot be guaranteed to be
> secure or error-free, as information could be intercepted, corrupted, lost,
> destroyed, arrive late, incomplete, or contain viruses. The sender,
> therefore, does not accept liability for any errors or omissions in the
> contents of this message which may arise as a result of email transmission.
> If verification is required, please request a hard-copy version.*
>



-- 
*Jawad Hassan*
Software Engineer
*Emblem Technologies (Pvt) Ltd*
*Uzair Pte Ltd, Singapore*
Skype: ja...@emblemtechnologies.com

LinkedIn  |
Twitter
 | Facebook 

*This message contains confidential information and is intended only for
the individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. Email transmission cannot be guaranteed to be
secure or error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late, incomplete, or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which may arise as a result of email transmission.
If verification is required, please request a hard-copy version.*
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] TtyUsb Yocto Issue

[Jawad Hassan]

Correction device_table


On Wed, Oct 9, 2013 at 5:44 AM, Jawad Hassan
wrote:

> PS. /etc/device_list does show a ttyUSB entry
>
>
> On Wed, Oct 9, 2013 at 5:36 AM, Jawad Hassan  > wrote:
>
>> Hi Paul,
>>
>> Thanks for your reply, but we're not seeing any ttyUSB* entries in the
>> /dev folder, the board is this one here:
>> http://boundarydevices.com/products/nitrogen6_lite/
>>
>> Which should have at least one port available for connection.
>>
>> But unfortunately we aren't seeing this device node. What should be our
>> way forward with this?
>>
>> Thanks in advance!
>>
>>
>> On Tue, Oct 8, 2013 at 9:04 AM, Paul Eggleton <
>> paul.eggle...@linux.intel.com> wrote:
>>
>>> Hi Jawad,
>>>
>>> On Tuesday 08 October 2013 06:43:18 Jawad Hassan wrote:
>>> > We're trying to access the USB serial port using rxtx on a java
>>> application
>>> > on Yocto. The problem is that we're unable to list out any ports on the
>>> > Nitrogen Lite board, we think this could be a permissions issue, if
>>> anyone
>>> > has been able to do this or any resources that can help us in getting
>>> this
>>> > done.
>>>
>>> It's hard to say for sure without further details, but assuming the
>>> device
>>> nodes actually exist in /dev and it's a typical device permissions issue
>>> there
>>> are two options:
>>>
>>> 1) Look at the /dev/ttyUSB* device nodes that exist and see if there is
>>> already a group assigned with write access; if so you just need to
>>> ensure the
>>> user you are running as is a member of that group.
>>>
>>> 2) Create a udev rule to set the device permissions correctly. This
>>> would be a
>>> matter of creating a recipe to install an extra file to
>>> /etc/udev/rules.d that
>>> assigned the desired permissions. There are lots of HOWTOs out there on
>>> the
>>> web for this, e.g.:
>>>
>>>
>>> http://sourceforge.net/apps/mediawiki/gizmod/index.php?title=HOWTO_-_Setting_Input_Device_Permissions_-_Creating_a_udev_Rule
>>>
>>> Cheers,
>>> Paul
>>>
>>> --
>>>
>>> Paul Eggleton
>>> Intel Open Source Technology Centre
>>>
>>
>>
>>
>> --
>> *Jawad Hassan*
>> Software Engineer
>> *Emblem Technologies (Pvt) Ltd*
>> *Uzair Pte Ltd, Singapore*
>> Skype: ja...@emblemtechnologies.com
>>
>> LinkedIn  | 
>> Twitter
>>  | Facebook 
>>
>> *This message contains confidential information and is intended only for
>> the individual named. If you are not the named addressee, you should not
>> disseminate, distribute or copy this email. Please notify the sender
>> immediately by email if you have received this email by mistake and delete
>> this email from your system. Email transmission cannot be guaranteed to be
>> secure or error-free, as information could be intercepted, corrupted, lost,
>> destroyed, arrive late, incomplete, or contain viruses. The sender,
>> therefore, does not accept liability for any errors or omissions in the
>> contents of this message which may arise as a result of email transmission.
>> If verification is required, please request a hard-copy version.*
>>
>
>
>
> --
> *Jawad Hassan*
> Software Engineer
> *Emblem Technologies (Pvt) Ltd*
> *Uzair Pte Ltd, Singapore*
> Skype: ja...@emblemtechnologies.com
>
> LinkedIn  | 
> Twitter
>  | Facebook 
>
> *This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee, you should not
> disseminate, distribute or copy this email. Please notify the sender
> immediately by email if you have received this email by mistake and delete
> this email from your system. Email transmission cannot be guaranteed to be
> secure or error-free, as information could be intercepted, corrupted, lost,
> destroyed, arrive late, incomplete, or contain viruses. The sender,
> therefore, does not accept liability for any errors or omissions in the
> contents of this message which may arise as a result of email transmission.
> If verification is required, please request a hard-copy version.*
>



-- 
*Jawad Hassan*
Software Engineer
*Emblem Technologies (Pvt) Ltd*
*Uzair Pte Ltd, Singapore*
Skype: ja...@emblemtechnologies.com

LinkedIn  |
Twitter
 | Facebook 

*This message contains confidential information and is intended only for
the individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. Email transmission cannot be guaranteed to be
secure or error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late, incomplete, or contain viruses. The sende

Re: [yocto] TtyUsb Yocto Issue

[Paul Eggleton]

On Wednesday 09 October 2013 05:36:37 Jawad Hassan wrote:
> Thanks for your reply, but we're not seeing any ttyUSB* entries in the /dev
> folder, the board is this one here:
> http://boundarydevices.com/products/nitrogen6_lite/

I have no personal experience with this board I'm afraid.

> Which should have at least one port available for connection.
> 
> But unfortunately we aren't seeing this device node. What should be our way
> forward with this?

I would assume either the kernel is not configured to enable the driver for 
these devices, or udev is not configured to create the appropriate device 
nodes.

I think perhaps the best thing would be to talk to someone who has worked on 
the support for this specific hardware. You might try asking about this on the 
meta-fsl-arm list.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] clarification on what packages are *truly* needed for a yocto build?

[Trevor Woerner]

On 9 October 2013 06:45, Robert P. J. Day  wrote:
> (for example, i would assume
> that, in any current distro, git would certainly be safe, no?)


The safety of a utility is only one consideration, feature-set is another.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: java cross compilation

[sonia verma]

Hi All,

I need to cross compile openjdk-7-jre in ppc64 platform using Yocto.

After setting the environment i am running "bitbake openjdok-7-jre" command
but i am getting following error message:

BB_VERSION= "1.18.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.10"
TARGET_SYS= "powerpc-fsl_networking-linux"
MACHINE   = "t4240rdb"
DISTRO= "fsl-networking"
DISTRO_VERSION= "1.4"
TUNE_FEATURES = "m32 fpu-hard e6500 altivec"
TARGET_FPU= "hard"
meta
meta-yocto
meta-yocto-bsp= "sdk-v1.4.x:16bfcaa96c074aac0a1f66d33b45fb33ba559325"
meta-fsl-ppc  = "sdk-v1.4.x:324b1cb7fadce0bbf145b922ce2e1d9af9ba223b"
meta-fsl-ppc-toolchain =
"sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723"
meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93"
meta-fsl-networking = "(nobranch):77405d17c48607551e4f095fb2f79eb0c09b8430"
meta-oe
meta-networking   = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616"
meta-java = "master:de06956f93ecd15d8c941a05da47a4425e3d397a"

NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-jre)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-common)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-jre)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-java)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item java2-runtime)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item java2-vm)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL
http://archive.apache.org/dist/ant/source/apache-ant-1.8.1-src.tar.gz,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, no output
ERROR: Function failed: Fetcher failure for URL: '
http://archive.apache.org/dist/ant/source/apache-ant-1.8.1-src.tar.gz'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/build_t4240rdb_release/tmp/work/i686-linux/ant-native/1.8.1-r1/temp/log.do_fetch.13403

ERROR: Task 209
(/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/meta-java/recipes-core/ant/
ant-native_1.8.1.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1182 tasks of which 902 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:

/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/meta-java/recipes-core/ant/
ant-native_1.8.1.bb, do_fetch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


Please help me on fixing this issue.


Thanks.
Sonia
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Creating BSP without using git

[Dilip KumarB]

Hi,
I need to create a local BSP layer using Yocto-bsp create command 
without the use of Git.


yocto-bsp create mylayers qemu -s
Which qemu architecture would you like to use? [default: i386]
1) i386(32-bit)
2) x86_64  (64-bit)
3) ARM (32-bit)
4) PowerPC (32-bit)
5) MIPS(32-bit)
3
Would you like to use the default (3.8) kernel? (y/n) [default: y] y
Do you need a new machine branch for this BSP (the alternative is to re-use an 
existing branch)? [y/n] [default: y] n
Getting branches from remote repo 
git://git.yoctoproject.org/linux-yocto-3.8.git...


Thanks with Regards
-
Dilip Kumar B | PES
L&T Infotech, Plot No. 25-31, EPIP 2nd Phase, KIADB Indl Area, Whitefield, 
Bangalore - 66
Off: 91-80-66242053
dilip.kum...@lntinfotech.com




The contents of this e-mail and any attachment(s) may contain confidential or 
privileged information for the intended recipient(s). Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail and 
using or disseminating the information, and must notify the sender and delete 
it from their system. L&T Infotech will not accept responsibility or liability 
for the accuracy or completeness of, or the presence of any virus or disabling 
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] java cross compilation

[sonia verma]

Hi All,

I need to cross compile openjdk-7-jre in ppc64 platform using Yocto.

After setting the environment i am running "bitbake openjdok-7-jre" command
but i am getting following error message:

BB_VERSION= "1.18.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.10"
TARGET_SYS= "powerpc-fsl_networking-linux"
MACHINE   = "t4240rdb"
DISTRO= "fsl-networking"
DISTRO_VERSION= "1.4"
TUNE_FEATURES = "m32 fpu-hard e6500 altivec"
TARGET_FPU= "hard"
meta
meta-yocto
meta-yocto-bsp= "sdk-v1.4.x:16bfcaa96c074aac0a1f66d33b45fb33ba559325"
meta-fsl-ppc  = "sdk-v1.4.x:324b1cb7fadce0bbf145b922ce2e1d9af9ba223b"
meta-fsl-ppc-toolchain =
"sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723"
meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93"
meta-fsl-networking = "(nobranch):77405d17c48607551e4f095fb2f79eb0c09b8430"
meta-oe
meta-networking   = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616"
meta-java = "master:de06956f93ecd15d8c941a05da47a4425e3d397a"

NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-jre)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-common)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-jre)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item openjdk-7-java)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item java2-runtime)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: preferred version 03b21-2.1.8 of openjdk-7-jre not available (for
item java2-vm)
NOTE: versions of openjdk-7-jre available: 25b30-2.3.12
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL
http://archive.apache.org/dist/ant/source/apache-ant-1.8.1-src.tar.gz,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, no output
ERROR: Function failed: Fetcher failure for URL: '
http://archive.apache.org/dist/ant/source/apache-ant-1.8.1-src.tar.gz'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/build_t4240rdb_release/tmp/work/i686-linux/ant-native/1.8.1-r1/temp/log.do_fetch.13403

ERROR: Task 209
(/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/meta-java/recipes-core/ant/
ant-native_1.8.1.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1182 tasks of which 902 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:

/home/anuj/freescale_1.4/QorIQ-SDK-V1.4-20130814-yocto/meta-java/recipes-core/ant/
ant-native_1.8.1.bb, do_fetch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


Please help me on fixing this issue.


Thanks.
Sonia
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH 0/5] Remove python dependency from refpol.

[flihp]

The reference policy package currently pulls in a lot of python stuff
that isn't strictly necessary to boot an SELinux system and load a
policy. This is caused by the mix of python and C utilities in
policycoreutils.

This patch set breaks the policycoreutils recipe up into multiple
packages, one for each utility. In this way we can have the refpol etc
pull in only the utilities necessary for normal operation. This happens
to be only the utilities written in C and thus we can remove python
completely in a minimal image.

I've attempted to localize these changes as much as possible so changes
in this patchset outside of the policycoreutils recipe are few. An
example image reicpe is added to demonstrate a minimal image with only
the utilities required to load a policy and manipulate the policy store
(add / remove policy modules) at runtime.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] dleyna not building

[Jean-Charles]

Hi,

Anyone tried to build dleyna recently ? The do_configure invariably 
fails on dylan (with a very long configure log but nothing obvious.. 
however a simple "bitbake media-service-upnp" will lead to the same error.


I suspect the package is somewhat outdate as I had to change the MD5 to 
be able to build it:


-SRC_URI[md5sum] = "9fc4db84b3459bc77232b24bde48b000"
-SRC_URI[sha256sum] = 
"9cdee47bbbfa3de5aaa5cf3fc9e208ccd97e5079f6d8fa84a6d1f24a1b760237"

+SRC_URI[md5sum] = "eb7d58a429184180fdc48330bba9bb45"
+SRC_URI[sha256sum] = 
"979661e4828a23292f05e9b82707d291fe2a63eeddcde0150a2f09c5c060847f"



Regards,
J.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dleyna not building

[Burton, Ross]

On 9 October 2013 12:48, Jean-Charles  wrote:
> Anyone tried to build dleyna recently ? The do_configure invariably fails on
> dylan (with a very long configure log but nothing obvious.. however a simple
> "bitbake media-service-upnp" will lead to the same error.
>
> I suspect the package is somewhat outdate as I had to change the MD5 to be
> able to build it:
>
> -SRC_URI[md5sum] = "9fc4db84b3459bc77232b24bde48b000"
> -SRC_URI[sha256sum] =
> "9cdee47bbbfa3de5aaa5cf3fc9e208ccd97e5079f6d8fa84a6d1f24a1b760237"
> +SRC_URI[md5sum] = "eb7d58a429184180fdc48330bba9bb45"
> +SRC_URI[sha256sum] =
> "979661e4828a23292f05e9b82707d291fe2a63eeddcde0150a2f09c5c060847f"

That's github re-generating tarballs underneath us - this was fixed in
meta-oe master by changing  it to do a git clone.  If you're using the
dylan stable branch you can cherry-pick that commit from master.

Then if you still get problems please paste the full logs, as I built
it all recently when changing the SRC_URI.

Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dleyna not building

[Jean-Charles]

On 09/10/2013 16:59, Burton, Ross wrote:

On 9 October 2013 12:48, Jean-Charles  wrote:

Anyone tried to build dleyna recently ? The do_configure invariably fails on
dylan (with a very long configure log but nothing obvious.. however a simple
"bitbake media-service-upnp" will lead to the same error.

I suspect the package is somewhat outdate as I had to change the MD5 to be
able to build it:

-SRC_URI[md5sum] = "9fc4db84b3459bc77232b24bde48b000"
-SRC_URI[sha256sum] =
"9cdee47bbbfa3de5aaa5cf3fc9e208ccd97e5079f6d8fa84a6d1f24a1b760237"
+SRC_URI[md5sum] = "eb7d58a429184180fdc48330bba9bb45"
+SRC_URI[sha256sum] =
"979661e4828a23292f05e9b82707d291fe2a63eeddcde0150a2f09c5c060847f"

That's github re-generating tarballs underneath us - this was fixed in
meta-oe master by changing  it to do a git clone.  If you're using the
dylan stable branch you can cherry-pick that commit from master.

Then if you still get problems please paste the full logs, as I built
it all recently when changing the SRC_URI.

Ross

the issue is with gssdp :

>> configure: error: Package requirements (gssdp-1.0 >= 0.13.2) were 
not met:

>> Requested 'gssdp-1.0 >= 0.13.2' but version of gssdp-1.0 is 0.12.2.1

There are both recipes on meta-multimedia, why would it take the older 
one :( ?

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dleyna not building

[Burton, Ross]

>>> Requested 'gssdp-1.0 >= 0.13.2' but version of gssdp-1.0 is 0.12.2.1
>
> There are both recipes on meta-multimedia, why would it take the older one
> :( ?

Because 0.13.2 is marked as a development release.  You'll need to set
PREFERRED_VERSION_gssdp = "0.13.2" (ditto for gupnp, probably).

Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dleyna not building

[Jean-Charles]

On 09/10/2013 17:11, Burton, Ross wrote:

PREFERRED_VERSION_gssdp = "0.13.2"
I just figured this by checking the two recipes. I'll try again wth this 
added to my conf



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is there anything like FILES_${PN}_append??

[Chris Larson]

On Wed, Oct 9, 2013 at 1:24 AM, Amit Tomer  wrote:

> Now for variable SRC_URI ,I can do something like SRC_URI_append_xyz where
> xyz is my platform where changes should be reflected.
>

This isn't specific to SRC_URI, it's general bitbake syntax that works for
any variable.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Qt + phonon + iMX codecs

[Jose Mª Ferreiro]

Hello

Here: iMX6Q Sabre Lite board + yocto - dylan+ linux-imx

One of our Qt tests is an application with four videos played by phonon. 
When we tried to make it work, we saw only one video working.


Looking for a solution we found the file 
0001-Add-support-for-i.MX-codecs-to-phonon.patch at
 dylan/sources/meta-fsl-arm/recipes-qt/qt4/qt4 directory. It used only 
mfw_v4lsink.


We changed  "mfw_v4lsink" references to "mfw_isink" (agressive, I know, 
but I was desperate)  ... and it worked. We had four videos on window.


Now, we are testing dora. Theres is another patch but the previous doing 
does not get the same result. I would say there are allocation memory 
problems and not all the videos are working. Sometimes one play, 
sometimes three, never four.


Can you give me any advice about how to add isink codec to phonon 
backend? or is it  being done now?


Thank you and best regards,
Jose




___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Ryan Kirkpatrick]

On Tue, 8 Oct 2013, Paul Eggleton wrote:

> Have you sent these fixes to the layer maintainer - Autif Khan 
> (autif.ml...@gmail.com) ? It would be good to get those integrated.

Yes, I did shortly after my post to the list, but I have not heard any 
response. 

Since then I have run into some issues with Mono v2.10 itself and my 
company's existing (proprietary) code base. It is an odd issue around 
events and a complex class hierarchy that I had encountered in the past 
with Mono v2.4 (but not v2.2). I traced it down to a single change in Mono 
and backed out that change for the previous product (an embedded server). 
I did report it to the Mono list at that time, but there was no simple 
test case I could share.

Anyway, I did a quick test with Mono v3.2 (from their web site on OS X) 
and the issues were no longer present. Hence, for the new product that I 
plan to use Yocto to develop, I am going to use Mono v3.2. Of course the 
current Mono layer has a lot more than we need (which is only the runtime 
and corelib, no X, xsp, etc...) but only includes support through v2.11. I 
am currently considering whether updating the existing meta-mono layer for 
v3.2 or just writing a quick recipe for just want we need from Mono.

This is complicated by a quick attempt to build the existing Mono layer 
for ARM failing. The failure was on the ARM objcopy not knowing what to do 
with mcs.exe.so as it is .NET assembly wrapped as an i386 shared object. 
This was during the generation of the debug package files, so looks like 
that process needs to be tweaked to understand this special case. 

I would welcome any advice on how to proceed with Mono v3.2 recipes and 
for building on ARM. Thanks!

---
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] 1.5 buildout and testing.

[Flanagan, Elizabeth]

All,

During the setup of yesterdays buildout of the final rc for 1.5, I
accidentally set the location for artifacts publishing to rc6. While
we could probably sort this all out due to mtime, I would rather us
have a clean build that doesn't taint the QA process with regards to
artifacts.

Tonight, when the autobuilders come back up, I will be rebuilding 1.5.
The build should be relatively quick from sstate. Please continue
build testing, but pause on testing artifacts. I will send an email
with the location of the new artifacts later tonight.

-b

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Recipes that update a shared file

[seth bollinger]

Hello All,

What's the best practice for recipes that need to update a shared file 
provided by a different recipe?  For example let's say that the 
widget-watcher recipe creates /etc/ww.conf and the widget1, and widget2 
recipes need to append a line to the config.  I've searched through the 
recipes a bit and can't find a good example.  The closest that I've seen 
is pkg_postinst().  Is that the best method?


Thanks!

Seth
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is there anything like FILES_${PN}_append??

[Amit Tomer]

Thanks Chris for your response

So you mean to say I can apply it to FILES_${PN}
IS something like FILES_${PN}_append_xyz fine??

On Wed, Oct 9, 2013 at 9:54 PM, Chris Larson  wrote:
>
> On Wed, Oct 9, 2013 at 1:24 AM, Amit Tomer  wrote:
>>
>> Now for variable SRC_URI ,I can do something like SRC_URI_append_xyz where
>> xyz is my platform where changes should be reflected.
>
>
> This isn't specific to SRC_URI, it's general bitbake syntax that works for
> any variable.
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto