<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git, branch 2.1_M1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=2.1_M1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=2.1_M1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2015-12-10T00:13:13+00:00</updated>
<entry>
<title>poky.conf: Bump for 2.1 development</title>
<updated>2015-12-10T00:13:13+00:00</updated>
<author>
<name>Beth Flanagan</name>
<email>elizabeth.flanagan@intel.com</email>
</author>
<published>2015-12-09T14:38:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e'/>
<id>urn:sha1:5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e</id>
<content type='text'>
(From meta-yocto rev: 45dd622d7447050e0c9caa067cce87d125518117)

Signed-off-by: Beth Flanagan &lt;elizabeth.flanagan@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: toasterui Add ParseStarted/ParseProgress events to mask</title>
<updated>2015-12-09T09:03:35+00:00</updated>
<author>
<name>brian avery</name>
<email>avery.brian@gmail.com</email>
</author>
<published>2015-11-17T16:47:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7e8ff7b9d793b7be106415c3c80b687977217566'/>
<id>urn:sha1:7e8ff7b9d793b7be106415c3c80b687977217566</id>
<content type='text'>
Toaster is not able to see ParseStarted and ParseProgress events
for command-line builds. This means it's not possible for Toaster
to detect failed builds, if the failure occurs at a point before
the BuildStarted event, as the build won't show up at all.

Add these events to the event mask, so that Toaster's toasterui
can detect and respond to them.

(Bitbake rev: 16bfd3e3d145705a2b3a05648ddbcacc7a338dfa)

Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>build-appliance-image: Update to master head revision</title>
<updated>2015-12-09T08:49:20+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-12-09T08:49:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f823601845597df59b7951a728ea0371a28102cd'/>
<id>urn:sha1:f823601845597df59b7951a728ea0371a28102cd</id>
<content type='text'>
(From OE-Core rev: 192da885e92d3b163b9c4e6b8151c9ecc6062b14)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto: Update genericx86* BSPs to v4.1.13</title>
<updated>2015-12-09T08:48:26+00:00</updated>
<author>
<name>Saul Wold</name>
<email>sgw@linux.intel.com</email>
</author>
<published>2015-12-01T23:12:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=992e5774714ef44bc91d45e2aaf2acfc23c72d63'/>
<id>urn:sha1:992e5774714ef44bc91d45e2aaf2acfc23c72d63</id>
<content type='text'>
Update the 4.1 kernel to the lastest stable for the generixx86 meta-yocto-bsps

(From meta-yocto rev: 7e81049a6bf06e970ff434acecb278966048ce3a)

Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cmake: Add nios2 support</title>
<updated>2015-12-09T08:48:26+00:00</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2015-11-26T20:43:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b4f6950451a133284fd0d754dfdb280b3f8daec6'/>
<id>urn:sha1:b4f6950451a133284fd0d754dfdb280b3f8daec6</id>
<content type='text'>
Add the necessary bits for nios2 support into cmake.

(From OE-Core rev: f6217be489d03cd72655f9457d4e7e21a097a9a7)

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Cc: Ley Foon Tan &lt;lftan@altera.com&gt;
Cc: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Cc: Ross Burton &lt;ross.burton@intel.com&gt;
Cc: Thomas Chou &lt;thomas@wytron.com.tw&gt;
Cc: Walter Goossens &lt;waltergoossens@home.nl&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>boost: adjust hard-coded path after python3 upgrade</title>
<updated>2015-12-09T08:48:25+00:00</updated>
<author>
<name>Lukas Bulwahn</name>
<email>lukas.bulwahn@oss.bmw-carit.de</email>
</author>
<published>2015-12-07T07:36:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=27b9f041df92fd8438962c2104a7a5d9dff77ce5'/>
<id>urn:sha1:27b9f041df92fd8438962c2104a7a5d9dff77ce5</id>
<content type='text'>
When using `PACKAGECONFIG = "python"` in the boost recipe, `bitbake boost`
fails at do_compile with:

    ./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory
    compilation terminated.

This issue is due to the recent version upgrade from python 3.4 to 3.5:

701ec1977ced1bb08461e6de98b4f63d21cba8a6 python3: Upgrade from 3.4.3 to 3.5

The boost.inc file modifies the boost build configuration with a path
containing the python3 major version, which is hard-coded in the boost.inc
file. Hence after the python3 update, the path points to the outdated
location and it needs to be updated to the new location.

This issue was unrevealed by an internal continuous integration system
for the meta-ros application layer. Further manual bisecting lead to the
critical commit 701ec1977ced1bb08461e6de98b4f63d21cba8a6.

(From OE-Core rev: 0eefd38a13a6ecb35f26ed8cd16f0b36f2c5d652)

Signed-off-by: Lukas Bulwahn &lt;lukas.bulwahn@oss.bmw-carit.de&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sdk.py / OpkgSdk: remove_packaging_data() after install</title>
<updated>2015-12-09T08:48:25+00:00</updated>
<author>
<name>Haris Okanovic</name>
<email>haris.okanovic@ni.com</email>
</author>
<published>2015-12-01T15:22:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=639cadd6f9a1ec795443081d7f1ca1ab530d385a'/>
<id>urn:sha1:639cadd6f9a1ec795443081d7f1ca1ab530d385a</id>
<content type='text'>
Run remove_packaging_data() on both host and target sysroots to wipe
opkg state after install, similar to what RpmSdk does.

Use case:

Opkg may download local package indexes (I.e. file:// URLs) by
sym-linking them into /var/lib/opkg/lists/ instead of copying [1].
This leaves behind broken symlinks under the lists directory when
using opkg to build SDK sysroots.

The -h option may be set via SDKTAROPTS in some configurations to create
symlink-less SDK archives for Windows file systems. Sysroots containing
broken symlinks will fail to archive under this configuration.

Testing:

Verified /var/lib/opkg/ is empty after running populate_sdk() in a Fido
based distribution.

[1] http://git.yoctoproject.org/cgit/cgit.cgi/opkg/commit/?h=opkg-0.3.x&amp;id=f9022a8520fcde8f1b71424d26a652c218fce685

(From OE-Core rev: c8e0ec2da9ad4ce1c103966906a85f68c15400dd)

Signed-off-by: Haris Okanovic &lt;haris.okanovic@ni.com&gt;
Reviewed-by: Alejandro del Castillo &lt;alejandro.delcastillo@ni.com&gt;
Natinst-ReviewBoard-ID: 119065
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>devtool: extract: update SRCTREECOVEREDTASKS for kernel</title>
<updated>2015-12-09T08:48:25+00:00</updated>
<author>
<name>Markus Lehtonen</name>
<email>markus.lehtonen@linux.intel.com</email>
</author>
<published>2015-12-03T13:54:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fd4894fcb44d1abef1dcc3a6a44bc78b2dbdf45a'/>
<id>urn:sha1:fd4894fcb44d1abef1dcc3a6a44bc78b2dbdf45a</id>
<content type='text'>
Add 'do_kernel_configme' and 'do_kernel_configcheck' to
SRCTREECOVEREDTASKS of kernel packages. These tasks should not be run
because kernel meta in the srctree is not necessarily up-to-date or
even present which causes build failures and/or invalid kernel config.
Especially so because 'do_patch' which is a dependency of
'do_kernel_configme' is not being run.

We now store .config in the srctree and 'do_configure' task is able to
run successfully.

(From OE-Core rev: 7ce4c18a4ba1ebcb9f46e652a881ace1f21d2292)

Signed-off-by: Markus Lehtonen &lt;markus.lehtonen@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>devtool: extract: copy kernel config to srctree</title>
<updated>2015-12-09T08:48:25+00:00</updated>
<author>
<name>Markus Lehtonen</name>
<email>markus.lehtonen@linux.intel.com</email>
</author>
<published>2015-12-03T13:54:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=34f1d819f4e08ccaad9baae7a05c744f4089345e'/>
<id>urn:sha1:34f1d819f4e08ccaad9baae7a05c744f4089345e</id>
<content type='text'>
This makes the correct kernel config to be used when building kernel
from srctree (extrernalsrc). If no kernel config is present in the
builddir 'do_configure' task copies .config from the srctree.

(From OE-Core rev: 3b516332e038a587685f6e0c14a7f04990bdd6cc)

Signed-off-by: Markus Lehtonen &lt;markus.lehtonen@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>lib/oe/package_manager: Introducing PACKAGE_FEED_BASE_PATHS/PACKAGE_FEED_ARCHS</title>
<updated>2015-12-09T08:48:25+00:00</updated>
<author>
<name>Leonardo Sandoval</name>
<email>leonardo.sandoval.gonzalez@linux.intel.com</email>
</author>
<published>2015-10-05T13:12:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6650357f13a52ad6a789cd79ec283218537c4aba'/>
<id>urn:sha1:6650357f13a52ad6a789cd79ec283218537c4aba</id>
<content type='text'>
The recently introduced PACKAGE_FEED_PREFIX is not flexible enough for
constructing URIs, because the same PREFIX is used for all PACKAGE_FEED_URIS.
Also, the string 'PREFIX' is confusing because it is not at the beginning of
the URI. The variable PACKAGE_FEED_BASE_PATHS replaces PACKAGE_FEED_PREFIX,
allowing multiple base paths to be appended on each PACKAGE_FEED_URIS. In the
other hand, a new variable called PACKAGE_FEED_ARCHS, similar in concept to
PACKAGE_BASE_PATHS, defines package architectures defined by the user.

To demonstrate the usage of the PACKAGE_FEED_URIS, PACKAGE_FEED_BASE_PATHS and
PACKAGE_FEED_ARCHS, let's assume these variables are set on local.conf

    PACKAGE_FEED_URIS = "https://example.com/packagerepos/release \
                         https://example.com/packagerepos/updates"
    PACKAGE_FEED_BASE_PATHS = "rpm rpm-dev"
    PACKAGE_FEED_ARCHS = "all core2-64"

the resulting feeds would be

    https://example.com/packagerepos/release/rpm/all
    https://example.com/packagerepos/release/rpm/core2-64
    https://example.com/packagerepos/release/rpm-dev/all
    https://example.com/packagerepos/release/rpm-dev/core2-64
    https://example.com/packagerepos/updates/rpm/all
    https://example.com/packagerepos/updates/rpm/core2-64
    https://example.com/packagerepos/updates/rpm-dev/all
    https://example.com/packagerepos/updates/rpm-dev/core2-64

(From OE-Core rev: 229723a20095e80bde29e4b3398047f62f972170)

Signed-off-by: Leonardo Sandoval &lt;leonardo.sandoval.gonzalez@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
