The first milestone release for Yocto Project 2.1 is available for
download now.
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.1_M1/
Thank you to everyone for your contributions.
eclipse-poky/kepler-master cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
eclipse-poky/luna-master 45
From: Wenzong Fan
Update git repos rev to latest stable release and use PV to indicate
the exact release version just like all of the *_git.bb recipes has
been done in oe-core.
ref: https://github.com/TresysTechnology/refpolicy/wiki
Signed-off-by: Wenzong Fan
---
recipes-security/refpolicy/re
On 01/06/16 17:42, Mark Hatle wrote:
> But using a combination of the defined dependencies and the layer index you
> should be able to resolve "known" layers. (Would also be nice if the index
> looked for collisions as well...)
I wrote a silly script[1] that probes the layer index and presents th
On 01/06/2016 05:07 PM, Haris Okanovic wrote:
> When set, this option disables interception and deferral of certain
> utilities (E.g. depmod, ldconfig) when called from maintainer scripts
> (E.g. postinst). Disabled by default to maintain old behavior.
>
> Append "option disable_intercepts 1" to
On 01/04/2016 05:45 PM, Haris Okanovic wrote:
> Usage: opkg-graph-deps [-h] [-o feed.dot] [-u ] Packages>
>
> Generates a dot formatted dependency graph of an IPK feed.
>
> The feed is specified by a list of IPK index (Packages) files, which
> are sourced in the order specified to build a depe
When set, this option disables interception and deferral of certain
utilities (E.g. depmod, ldconfig) when called from maintainer scripts
(E.g. postinst). Disabled by default to maintain old behavior.
Append "option disable_intercepts 1" to opkg.conf to set it.
Testing:
* Installed package conta
On 1/6/16 2:41 PM, Andrei Gherzan wrote:
> Hello all,
>
> We started a discussion at the last ELCE: layer manifest in a machine parsable
> format. I'll make a short summary on what is this about.
>
> In the current yocto layers structures, the only way to describe a layer is
> through README. Whi
On 12/22/2015 03:40 AM, Simon Ruetzler wrote:
> Hello,
> I want to create different packages from one recipe.
>
> This is working except for one package.
> I addes this package with
> PACKAGES += " ${PN}-demo"
> and I expected that it is named with the recipe name and demo. In this case
> rumo-c
Ping - any updates on this? I've tried a lot of ways to fix it, but I can't
seem to get it to compile at all...
On Wed, Dec 30, 2015 at 3:28 PM Giordon Stark wrote:
> Here's an update set of logs:
>
> (output) https://gist.github.com/anonymous/56f904b65feeb3346db6
> (CMakeError.log) https://gist
Hello all,
We started a discussion at the last ELCE: layer manifest in a machine
parsable format. I'll make a short summary on what is this about.
In the current yocto layers structures, the only way to describe a layer is
through README. Which provides useful information like layer dependencies,
Hi,
I am working on integrating rsyslog's IMJournal module to my yocto based
platform.
I have package_config in my bitbake file for rsyslog as follows,
# first line is default yes in configure
PACKAGECONFIG ??= " \
zlib rsyslogd rsyslogrt klog inet regexp uuid libgcrypt \
imdiag gnutls im
On 6 January 2016 at 04:07, Renjith Vijayan wrote:
> checking for LIBSYSTEMD_JOURNAL... no
> | configure: error: Package requirements (libsystemd-journal >= 197) were
> not met:
> |
> | No package 'libsystemd-journal' found
> |
> | Consider adjusting the PKG_CONFIG_PATH environment variable if yo
12 matches
Mail list logo
