[yocto] Weekly build soon available

2014-05-07 Thread Flanagan, Elizabeth
The most recent weekly will soon be available at: http://autobuilder.yoctoproject.org/pub/nightly/20140506-3 bitbake 4eb2dc8048e2722d64d589f453df1ce6262c71b8 eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37 eclipse-poky-kepler 1dfe1d2f1322b5fda8e1a7637c447b0e060efb3e meta-fsl-arm

[yocto] Smart/RPM automatic feed configuration

2014-05-07 Thread Alex J Lennon
I'm using RPM package feeds with smart, and am wondering how to configure up the feed sources easily at build time? I see in 3.4.5 of the reference manual it talks about base-feeds.conf for opkg but I'm wondering if there's a variable I can set in local.conf to correct setup, say, the URL prefix

[yocto] Fwd: [meta-security][PATCH] nmap: inherit autotools-brokensep to allow B=S build.

2014-05-07 Thread Nick D'Ademo
-- Forwarded message -- From: Nick D'Ademo nickdad...@gmail.com Date: Wed, May 7, 2014 at 8:26 AM Subject: Re: [meta-security][PATCH] nmap: inherit autotools-brokensep to allow B=S build. To: Yocto list discussion yocto@yoctoproject.org This is a resubmission - added required

[yocto] replace udhcpc

2014-05-07 Thread Neuer User
Hi I encounter a problem with the DHCP network setup during boot: System starts. During start ifup is called. ifup calls udhcpc. Network is, however, not yet up! udhcpc exits with failure. Then network is up. But, of course, no connection, because no IP address. In earlier times I used debian

Re: [yocto] Smart/RPM automatic feed configuration

2014-05-07 Thread Alex J Lennon
On 07/05/2014 07:49, Alex J Lennon wrote: I'm using RPM package feeds with smart, and am wondering how to configure up the feed sources easily at build time? I see in 3.4.5 of the reference manual it talks about base-feeds.conf for opkg but I'm wondering if there's a variable I can set in

Re: [yocto] replace udhcpc

2014-05-07 Thread Søren Holm
Use ifplugd recipe I just submitted. Onsdag den 7. maj 2014 10:57:22 skrev Neuer User: Hi I encounter a problem with the DHCP network setup during boot: System starts. During start ifup is called. ifup calls udhcpc. Network is, however, not yet up! udhcpc exits with failure. Then network

Re: [yocto] Weekly build soon available

2014-05-07 Thread Richard Purdie
On Tue, 2014-05-06 at 23:34 -0700, Flanagan, Elizabeth wrote: The most recent weekly will soon be available at: http://autobuilder.yoctoproject.org/pub/nightly/20140506-3 bitbake 4eb2dc8048e2722d64d589f453df1ce6262c71b8 eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37

[yocto] [meta-networking][PATCH] ifplugd: Added ifplugd recipe.

2014-05-07 Thread Søren Holm
Signed-off-by: Søren Holm s...@sgh.dk --- .../ifplugd/files/ifplugd.conf | 42 ++ .../recipes-connectivity/ifplugd/ifplugd_0.28.bb | 23 2 files changed, 65 insertions(+) create mode 100644

Re: [yocto] replace udhcpc

2014-05-07 Thread Burton, Ross
On 7 May 2014 09:57, Neuer User auslands...@gmx.de wrote: What should I do best on Yocto? Replace udhcpc with dhclient? If so, how should that be done? Personally I prefer using connman for this, it does all the usual hotplug and connect magic. If size is an issue, you can disable the 3g and

Re: [yocto] A simpler way of creating an using a local kernel repository - BeagleBone example

2014-05-07 Thread Gary Thomas
On 2014-05-06 20:48, Bob Feretich wrote: On 5/6/2014 3:45 PM, Gary Thomas wrote: On 2014-05-06 16:31, Bob Feretich wrote: I have had problems getting good download performance when accessing the kernels at kernel.org. Since I expect to build the kernel several times, I decided to create a

Re: [yocto] Definition of Yocto tasks

2014-05-07 Thread Paul Eggleton
On Tuesday 06 May 2014 15:23:45 Bob Feretich wrote: On 5/6/2014 2:38 AM, Paul Eggleton wrote: On Tuesday 06 May 2014 06:47:08 Rifenbark, Scott M wrote: -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Bob Feretich

[yocto] linux-yocto custom device tree in overlay

2014-05-07 Thread Andreas Galauner
Hi Yocto Community, I'm currently trying to build a custom image for a beaglebone black for which I need to enable the can-controllers on the SoC. I managed to create an overlay which already deals with building a few tools for CAN communication, I created a kernel config snippet for linux-yocto

[yocto] [meta-selinux][PATCH] libsemanage: disable expand-check on policy load

2014-05-07 Thread Joe MacDonald
For small policy modules it's not necessary to walk the hierarchy on load. On embedded devices that are low-powered or resource-constrained disabling the hierarchy processing can make the difference between seconds and (many) minutes of load time (or being able to load the policy at all).

Re: [yocto] linux-yocto custom device tree in overlay

2014-05-07 Thread Bruce Ashfield
On 14-05-07 11:33 AM, Andreas Galauner wrote: Hi Yocto Community, I'm currently trying to build a custom image for a beaglebone black for which I need to enable the can-controllers on the SoC. I managed to create an overlay which already deals with building a few tools for CAN communication, I

[yocto] [v2][meta-selinux][PATCH 0/8] fix PRINC QA Warning

2014-05-07 Thread Joe MacDonald
An updated version of the series sent out by Hongxu Jia a few weeks back. Integrating the original series caused grief on some of my builders, so this is a modified approach, hopefully preserving the original credit and making it clear where I'm to blame. FWIW, there's been several stable

[yocto] [meta-selinux][PATCH 6/9] libselinux: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 2/9] libpcre_8.34.bbappend: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com The libpcre has been upgrade to 8.34 in oe-core, but since we were still using PRINC until now, we'll need to keep it around (in a PR form), so set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's

[yocto] [meta-selinux][PATCH 4/9] libsepol: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 8/9] refpolicy: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 9/9] linux-yocto: remove PRINC warning

2014-05-07 Thread Joe MacDonald
Convert PRINC to PR .= so as to not break package feeds. Next time this won't be necessary at all. Signed-off-by: Joe MacDonald j...@deserted.net --- recipes-kernel/linux/linux-yocto_3.10.bbappend |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[yocto] [meta-selinux][PATCH 3/9] sepolgen: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 7/9] checkpolicy: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 5/9] libsemanage: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

[yocto] [meta-selinux][PATCH 1/9] policycoreutils: remove PRINC warning

2014-05-07 Thread Joe MacDonald
From: Hongxu Jia hongxu@windriver.com Bump up PR and remove PRINC. Set it to something suitably large that it's unlikely to break anyone's package feed and so that it shows it's clearly an exception case. Obviously this is just a staging activity until the next update when we don't include

Re: [yocto] OEDAM: OpenEmbedded Developers (Americas) Meeting

2014-05-07 Thread Denys Dmytriyenko
The OpenEmbedded Board of Directors would like to thank everyone who was able to participate (either in person in Santa Clara or online) in our first OEDAM OpenEmbedded Developers (Americas) Meeting on May 2nd and 3rd! The meeting was a huge success and a lot of fun! We would also like to

Re: [yocto] DL_DIR problems

2014-05-07 Thread Taek Hyun Shin
If the problems is permission denied, you can try to that all developers change downloaded file's permission (chmod -R g+rw DL_DIR or chmod -R g+r DL_DIR) If break build, sometimes the downloaded file's permissions to be 0600. Wily Taekhyun Shin

Re: [yocto] replace udhcpc

2014-05-07 Thread Neuer User
Am 07.05.2014 11:27, schrieb Søren Holm: Use ifplugd recipe I just submitted. Very nice idea. Where do I find the recipe? Onsdag den 7. maj 2014 10:57:22 skrev Neuer User: Hi I encounter a problem with the DHCP network setup during boot: System starts. During start ifup is called. ifup