Khronos documentation[1] says that include/GLES2/gl2ext.h can be used
for OpenGL ES 3 specification as well as for OpenGL ES 2.
There can be applications including GLES2/gl2ext.h instead of
GLES3/gl3ext.h meaning we should probably bring in GLES2/gl2ext.h if
someone asks for development package of libgles3.
[1] https://www.khronos.org/registry/OpenGL/index_es.php#headers
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From OE-Core rev: 8adf941a8a2b5b3fe5e4e3313856b725e28d5370)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
texturator requires GLES 3 headers and libs so let's explicit this
dependency. This was not detected until now because mesa, the default
provider, actually provides both Open GLES 2 and 3 compliant
implementations.
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From OE-Core rev: a8bac1006d87d0a702630607f6c46d2f4926776e)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It's assumed that not all OpenGL ES implementation are compliant with
the 3.x specification. Therefore an additional virtual providers is
created to explicit compatibility with OpenGL ES 3 specification.
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From OE-Core rev: 405cd7a37988ced627fe6ad6fd3089c17f59367e)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-Do-not-preserve-ownership-when-installing-example-jo.patch
removed since it is included in 0.13.08
(From OE-Core rev: 111de7be7336bc9c7919e7fc130fd9953e6e7250)
Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
================
Bugs fixed
----------
* Several incompatibilities with CPython 3.11 were resolved.
(Github issues #4411, #4414, #4415, #4416, #4420, #4428, #4473, #4479, #4480)
* Some C compiler warnings were resolved.
(Github issue #4439)
* C++ "std::move()" should only be used automatically in MSVC versions that support it.
(Github issue #4191)
* The "Py_hash_t" type failed to accept arbitrary "index" values.
(Github issue #2752)
* Avoid copying unaligned 16-bit values since some platforms require them to be aligned.
Use memcpy() instead to let the C compiler decide how to do it.
(Github issue #4343)
* Cython crashed on invalid truthiness tests on C++ types without "operator bool".
(Github issue #4348)
* The declaration of "PyUnicode_CompareWithASCIIString()" in "cpython.unicode" was incorrect.
(Github issue #4344)
(From OE-Core rev: 8d8faad71e05703362d4004cc9ecdb93c08398ec)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
====================
libmpg123: Catch more NULL pointer arguments in LFS wrappers
(most prominently: mpg123_feedseek(), bug 328).
mpg123:
-Fix regression that did _not_ enable --remote-err on -s anymore.
-Fix typos in man page.
-Drop mixed-up value limits on remote control SEQ command.
It is up to you if you want to distort your sound.
-Add note about equalizer frequency bands to man page.
-build: add BUILD_PROGRAMS option to ports/cmake
(From OE-Core rev: e4e84d295f774136900e0a09001d19cbeab1a157)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Disable tests to save some build time as we can't install them.
(From OE-Core rev: dc91910a5ee56af5dee495fafcabab4042431cae)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Yocto Project releases use a specific Bitbake release. Currently the
bitbake: mapping is pointing to the current master version of Bitbake
documentation. This is an issue if some links disappear over time and
someone is still building old documentation (which is the case on the YP
autobuilder for example). Also, the documentation at the current master
version of Bitbake might not be correct for the Yocto Project version
associated with the doc the user is currently looking at, potentially
causing confusion.
In master branch, nothing needs to be done. For release branches, the
bitbake_version variable needs to be set accordingly. See
https://wiki.yoctoproject.org/wiki/Releases for the mapping.
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From yocto-docs rev: 457a591a46c57519046f9e3f8bffd632bb2275ea)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three's been some feedback saying that people actually missed that
paragraph and thought creating the layer by hand was the only way to do
it instead of leveraging bitbake-layers create-layer tool.
Let's try to make it a bit more obvious one does not need to create the
layer by hand by putting the paragraph into a note.
(From yocto-docs rev: 2b171d267ae37d467f8437c4739f32e5253049b3)
Signed-off-by: Quentin Schulz <foss@0leil.net>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Except the name of variables which can't be changed only in the
documentation for obvious reasons and workflow or developement
explanations around the use of the "master" branch which cannot be
replaced with "development" branch instead, most of the non-inclusive
words that appear in https://inclusivenaming.org/word-lists/tier-1/
should have been replaced in this patch.
(From yocto-docs rev: 2755f35060084f7af356091de9dc144f85530fe2)
Signed-off-by: Quentin Schulz <foss+yocto@0leil.net>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes the manuals easier to use.
Note the care to keep the paths visible, so that people
reading a printed version still know where to find the files.
(From yocto-docs rev: 501917f65530f14ea686b69d6e96407c3f970a28)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These versions have reached their end of life
and we don't test them any more.
(From yocto-docs rev: e4ff50fadbf61bf29015e9eded2584731c5d2bb2)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are no more free updates to Ubuntu 16.04
We can no longer test the latest updates to this distro.
(From yocto-docs rev: 752636d8924f0aaae1e8df61affef3310ae91aa0)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This upgrades to the latest upstream version where our fixes have equivalent
fixes merged upstream so our patches are no longer needed.
(From OE-Core rev: 987077008c89a9086247d5bcdf35aef7413fb954)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: d772775b3f77a753e8401dba3b4a73d5246a290f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: 0610df3e56e350493731d49fe67261b62d346573)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: cba76eb9232df9af6b1b82649f3e0c6b99ce668c)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
This means that apr now installs libtool into the build-1 folder, but
as this has never been needed before (as we use the system libtool) we
can remove it (it contains build paths so is unreproducible). Also add
a RDEPENDS on libtool for the target -dev package.
(From OE-Core rev: 07c0c780fb79779827dcd7496fac288c179aa259)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: 000f129323e4fda3fed9d6d0e45f0bc0328a737e)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: 291654cb31ff3568f278d143510f1e9fac573966)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: df74f8637b63d3b88a1b5bdbca22503b98d2d54b)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libtool is now longer renamed to ${host}-libtool, so remove the changes
to support this.
(From OE-Core rev: 5a4088a1dce17886d391db25a667dd4e0dbbc5cb)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We update the libtool m4 files in binutils with the latest files from
our patched libtool so that we can use the --with-libtool-sysroot option.
Remove the chunks that are specific to the libtool renaming, which now
doesn't happen.
(From OE-Core rev: 30baaf6c20a2e1619439cf3eb8d9ce7cb877d2fa)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Typically libtool installs the binary to 'libtool' in the source tree,
but we've got patches to rename this to ${host_sys}-libtool. As this
isn't standard any upstream that don't respect the LIBTOOL variable need
to be told explicitly where libtool is, which is a long-term maintenance
burden for us on top of the initial libtool patches.
The reasoning for this renaming appears to stem from the design to be
sure that we're using our new/patched libtool and not the host's binary.
However, now that we have HOSTTOOLS, there's no way to run the host
libtool so this argument is moot.
This patch removes the libtool renaming, follow-up patches remove the
required modifications from the rest of the recipes.
[RP: Remove commented patch lines]
(From OE-Core rev: 4b308773eca7570ce5007e8f953b56252c17fdb1)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Originally issue:
building of glibc 2.32 or 2.34 with option "-Wl,--build-id"
produce libc.so.6 with section ".note.gnu.build-id" that have
invalid(double, 0x48) section size. It happens because glibc
use sublibraries for linking libc.so.6
ld produce this sublibraries with build-id section and on last
linking stage loads this sections as input for linking.
ld should create new(valid) ".note.gnu.build-id" into function
ldelf_setup_build_id on last linking stage but it skip creating because
build-id section already exists.
As result libc.so.6 contain ".note.gnu.build-id" with build-ids from
sublibraries and without valid build-id
Howto solved:
1. Discard input .note.gnu.build-id sections.
2. Clear the build ID field before writing.
3. Use bfd_make_section_anyway_with_flags to create the output
.note.gnu.build-id section.
Upstream-Status: Backport
Reference to upstream patch:
[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1f1d0f8888a6c944e612b416a2a6e11abcf5199f]
(From OE-Core rev: 68bbff44a481a036dc7d39e5d5745a01ccffdb95)
Signed-off-by: Valerii Chernous <vchernou@cisco.com>
Signed-off-by: Valery Chernous <valery.chernous@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New patch adds a knob to select needed shell interpreter for tzselect
script, which then we excercise via EXTRA_OEMAKE
(From OE-Core rev: 28adfbbcf42d15eabdd7fe3a5dea486bd5049f09)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Doing that should not change the task signatures.
(From OE-Core rev: a06ceaeaf11aa344e152f3bb6629aa6e000482d3)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Move helper functions out of class scope so they can be used in other tests
(From OE-Core rev: 439a5a575b8ca27910431c71f01bf310122ff7ab)
Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This class provides an image feature that mounts /etc as an overlayfs
file system. This is an extension for existing overlayfs class, which
doesn't support /etc
(From OE-Core rev: 610ea808c8b5edb2826bda1f1c42a811bd4ba758)
Signed-off-by: Alfred Schapansky <alfred.schapansky@avantys.de>
Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
