<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/conf, branch master-next2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master-next2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master-next2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2019-09-18T10:52:02+00:00</updated>
<entry>
<title>Remove SSTATE_HASHEQUIV_SERVER</title>
<updated>2019-09-18T10:52:02+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>jpewhacker@gmail.com</email>
</author>
<published>2019-09-16T17:49:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7342546a9a834b7e613ba81e7a18c95d88e6f163'/>
<id>urn:sha1:7342546a9a834b7e613ba81e7a18c95d88e6f163</id>
<content type='text'>
Removes all references to the SSTATE_HASHEQUIV_SERVER variable. This
variable is redundant now that BB_HASHSERVE is present.

(From OE-Core rev: fb74079c0a66a88aaa789d9a35bd5d188c369110)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tune-cortexa57-cortexa53: add tunes for ARM Cortex-A53-Cortex-A57</title>
<updated>2019-09-16T22:02:44+00:00</updated>
<author>
<name>Limeng</name>
<email>Meng.Li@windriver.com</email>
</author>
<published>2019-09-11T09:59:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1edc497a80fb967c5ccf5293b4f746645260b780'/>
<id>urn:sha1:1edc497a80fb967c5ccf5293b4f746645260b780</id>
<content type='text'>
commit 3613b2780a6b5d5d70ea6802be5060a8214cbdb5 from
git://github.com/renesas-rcar/meta-renesas

The renesas rcar SoC H3/M3 is big.LITTLE architecture(cortex-a57.cortex-a53).
In order to optimize the performance of the code running on SoC H3/M3,
add a tune file for ARM Cortex-A53-Cortex-A57.
Create this tune file by refering GCC doc, 3.18.5 ARM Options.

(From OE-Core rev: 7e0c9290a9971b92bcb313742f126ca7488d91c3)

Signed-off-by: Meng Li &lt;Meng.Li@windriver.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>conf/multilib.conf: Add ovmf to NON_MULTILIB_RECIPES</title>
<updated>2019-09-16T22:02:44+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2019-09-11T10:31:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6606a86979f596877b60184a81d7bfc3f06c1751'/>
<id>urn:sha1:6606a86979f596877b60184a81d7bfc3f06c1751</id>
<content type='text'>
Fixed:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

$ bitbake ovmf lib32-ovmf
[snip]
ERROR: ovmf-edk2-stable201905-r0 do_deploy_setscene: The recipe ovmf is trying to install files into a shared area when those files already exist.
 Those files and their manifest location are:
  /buildarea1/lyang1/rebase-work/test_cc/tmp-glibc/deploy/images/qemux86-64/OvmfPkKek1.key
    (matched in manifest-qemux86_64-lib32-ovmf.deploy)
[snip]

Add it NON_MULTILIB_RECIPES to fix the problem since it is a firmware, build
multilib for it doens't make much sense.

(From OE-Core rev: 5c685f55ccba9d47a79e8798903b30b90bdf03c6)

Signed-off-by: Robert Yang &lt;liezhi.yang@windriver.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>feature-arm-thumb.inc: fix ARM_THUMB_SUFFIX</title>
<updated>2019-09-07T06:47:24+00:00</updated>
<author>
<name>Andre McCurdy</name>
<email>armccurdy@gmail.com</email>
</author>
<published>2019-08-23T20:51:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=71fbb2077124c18f2ae2d26b07869c5a29a55edb'/>
<id>urn:sha1:71fbb2077124c18f2ae2d26b07869c5a29a55edb</id>
<content type='text'>
Since TUNE_FEATURES now either contains a CPU or an architecture (but
not both) we can't rely on finding the architecture in TUNE_FEATURES.
Use architecture specific over-rides instead.

(From OE-Core rev: 805dd4807d322dc70cef97edd68fdb3142b60fb1)

Signed-off-by: Andre McCurdy &lt;armccurdy@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>security_flags.inc: Add overrides for glibc-testsuite to match glibc</title>
<updated>2019-09-06T11:45:47+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2019-09-05T13:44:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e5fe46c4c09b4a73da0983328700311a63736a5e'/>
<id>urn:sha1:e5fe46c4c09b4a73da0983328700311a63736a5e</id>
<content type='text'>
Ensure glibc-testsuite has the same flags as glibc.

(From OE-Core rev: f8ab08441f90eb75295304c57746c6e5f907ca64)

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>glibc-testsuite: Create a recipe to implement glibc test suite</title>
<updated>2019-09-06T11:45:47+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2019-09-03T16:56:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=182267b3052de9539bd0a72ffdfc41e54ed3b298'/>
<id>urn:sha1:182267b3052de9539bd0a72ffdfc41e54ed3b298</id>
<content type='text'>
A recipe needs to be created for the test suite due to the dependency
chain between libgcc -&gt; glibc -&gt; libgcc-initial, and the requirements of
the test suite to have libgcc for compilation and execution.

The glibc test suite does not use dejagnu like the gcc test suites do.
Instead a test wrapper script is used along with the assumed dependency
of having the same filesystem available on build host and target. For
qemu linux-user the same filesystem is inherently available, for remote
targets NFS is used. Separate test wrapper scripts are created for qemu
linux-user or ssh targets, with the same TOOLCHAIN_TEST_* variables used for
configuration.

(From OE-Core rev: 6c4d581c35ebd51c4b080ac38175d93f0480f97d)

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>binutils-cross-testsuite: Create recipe for test suite execution</title>
<updated>2019-09-06T11:45:47+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2019-09-03T16:56:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9d00c56d5bb7d13485c68ebb17c9f493218860ca'/>
<id>urn:sha1:9d00c56d5bb7d13485c68ebb17c9f493218860ca</id>
<content type='text'>
Create the do_check task in a new recipe 'binutils-cross-testsuite'.
This recipe is built within a target recipe (not -cross) to ensure
correct testing against target specific libraries/etc. The do_check task
is used to execute the binutils test suite for the cross target
binutils. By default this executes tests for binutils, gas and ld. This
can however be changed by setting CHECK_TARGETS to the desired test
suite target (e.g. 'gas').

The binutils test suites do not require any target execution, as such
the check task can be run without QEMU or a target device. However
since the binutils tests do rely on a C compiler there is dependence on
both gcc and libc in order to run the tests.

(From OE-Core rev: 1fb98bfdccb82474176fe8fca616aea84475942e)

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dejagnu: Add dejagnu for binutils/gcc test suites</title>
<updated>2019-09-06T11:45:47+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2019-09-03T16:56:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f7194f29ce1b94782f9eae376456b149e2648e77'/>
<id>urn:sha1:f7194f29ce1b94782f9eae376456b149e2648e77</id>
<content type='text'>
The binutils and gcc test suites use dejagnu for execution. Copy the
dejagnu recipe from meta-oe, and update it to 1.6.2.

(From OE-Core rev: 72692268b0c578450b568cfc2527098673c1dbe0)

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Remove leftovers from the eglinfo removal</title>
<updated>2019-09-06T07:15:45+00:00</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@stusta.de</email>
</author>
<published>2019-09-05T17:19:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=31f5a835f58d4625c648534f605376b7f0105af8'/>
<id>urn:sha1:31f5a835f58d4625c648534f605376b7f0105af8</id>
<content type='text'>
(From OE-Core rev: 8d692de6a13f881e92c254fa60b18d8fe59be830)

Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Clean up remnants of glibc-initial</title>
<updated>2019-09-06T07:15:45+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2019-09-05T13:44:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1c115da44666f8ab1e39cd0b20111464b08ed945'/>
<id>urn:sha1:1c115da44666f8ab1e39cd0b20111464b08ed945</id>
<content type='text'>
Remove remnants of the glibc-initial recipe.

(From OE-Core rev: 332b1e21db3e0cbeeb14f12dd6aeedb89b76d761)

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
