Reformat patches using git, so that rebasing them to newer versions is easier.
(From OE-Core rev: 796f5a422a1bb9059ca8045b5aa199aa02b0e46a)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-Unset-need_charset_alias-when-building-for-musl.patch
0001-c-stack-stop-using-SIGSTKSZ.patch
0001-test-getopt-posix-fix.patch
m4-1.4.18-glibc-change-work-around.patch
deleted since they are included in 1.4.19
refresh ac_config_links.patch
License-update: URL of license changed
(From OE-Core rev: c61358d84d83f0fbd8b2fbe2659ed547e0c046a4)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With 1.7.2 it is not required any and although they mention glibc explicitly,
_GNU_SOURCE is set in config.h for musl either.
(From OE-Core rev: 976c4bb2b1ab75e3fe600a81adc451b698ea4b65)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Version 1.1.2 - This is a bug fix release, correcting a regression [1] introduced by and
improving the checks from the fix for CVE-2021-31535.
[1] https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/133
Alan Coopersmith (1):
libX11 1.7.2
Matthieu Herrb (2):
include <limits.h> always, not if HAVE_CONFIG_H is set.
Check for NULL strings before getting their lengths
Tobias Stoeckmann (1):
Protect against overly long strings
(From OE-Core rev: 2d98f8d257d31b334e70357093b6d2a355362688)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes:
build:
* Fix up the build to actually build all library objects with libtool
consistently, also ensuring no pointless static archives for output modules.
* Adapted things to autoconf 2.71, requiring 2.69 now (the latter tested on
Debian, with their patches).
* Improved configure to be more useful --with-default-audio to define the
search order, fix static build for --with-audio being a list (just choosing
the first one).
* Ensure consistent use of LINK_MPG123_DLL in headers.
build (ports/cmake):
* Thanks to Evgeni Poberezhnikov for working with us on that.
* Fix up ports/cmake to really work in MSVC also for users of the lib (tested
in vcpkg, bug 310).
* Hardcode ports/cmake CPU detection for x64 and ARM as CMAKE_SYSTEM_PROCESSOR
is useless crap (bug 298 for real).
* Add missing io.h for _setmode() MSVC warned about (bug 311).
* Added BUILD_NO_LARGENAME define to be used by MSVC builds. Note that an
MSVC build of libmpg123 does not support 64 bit file offsets. That would
need more morting to the explicit API. Thanks to MS for making off_t even
more messy and less useful.
* Added JACK output, fixed handling of compat_str there and in win32_wasapi.
libsyn123:
* Fix syn123_mix() to actually do intermediate conversion when input
and output encoding are the same but non-float. This makes out123 --mix work
with s16 input and output, which is not that special!
libmpg123:
* Fix misguided handling of part2_3_length checks in III_get_scale_factors_1()
and III_get_scale_factors_2() which invalidated decoding of a mono source
encoded as ms+i-stereo (bug 312). This was a regression introduced with
version 1.25.7.
libout123:
* Print basic module loading errors only for last one in list. This enables
use of an output module search list that anticipates module files not
installed with the main package.
* Fixes for win32_wasapi build with MSVC.
(From OE-Core rev: a4308b8959041a63896a01a5d79847805be5808d)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes:
* Bump inputproto to 2.3.99.2
* specs: Fix type of GESTURECLASS num_touches member
* specs: Fix type of TOUCHCLASS num_touches member
* Bump inputproto to 2.3.99.1
* specs: Specify XI 2.4 as unreleased
(From OE-Core rev: 1860cd0e36806d0a11dcbea52aafd017a68cf2f3)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes runtime problems with qemu-user
Fatal glibc error: CPU lacks float128 support (POWER 9 or later required)
(From OE-Core rev: 2a2ba9ec4ca1aeb4a1d5336bb18ab76253c87bc0)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix a slew of CVEs (CVE-2021-3544, CVE-2021-3545, CVE-2021-3546) by
backporting the relevant patches from qemu's git.
(From OE-Core rev: ce850a5ce84f949d3114024c89ae3dd98fcbef41)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch isn't yet upstream but it has been submitted and other distros
are shipping it.
(From OE-Core rev: ea33a4a2df4600a55b268e9d57e7396c30f3d123)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add runtime dependency on:
- python3-compression
- python3-json
- python3-statistics
Upstream release notes:
6.14.0 - 2021-06-09
The explain phase now requires shrinking to be enabled, and will be
automatically skipped for deadline-exceeded errors.
https://hypothesis.readthedocs.io/en/latest/changes.html#v6-14-0
(From OE-Core rev: 5a99655d4045cec83169136ca977e81c9123575a)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
cpython/Lib/statistics.py contains common statistics functions
"""
Basic statistics module.
This module provides functions for calculating statistics of data, including
averages, variance, and standard deviation.
"""
(From OE-Core rev: cf1c49fea90e11bc037025e15e44f705a12385bf)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids a confusion because of the way other manuals
are numbered, and aligns with the way the migration guides
are listed.
(From yocto-docs rev: 92f17a0ac68a64c86fa46ffbcec7acb3de3b23bf)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The definition of IMAGE_MANIFEST was moved to a different class. Fixup
the documentation to reflect this change.
(From yocto-docs rev: 15c0a09154de2a1f6d36e1bb5bf283bd08c9ec3d)
Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example for IMAGE_CMD_jffs2 given in the glossary for IMAGE_CMD
didn't align with the implementation anymore. Update it to match the
implementation.
(From yocto-docs rev: 4db4efc42af89a109313c4cf33ae13e8236215e9)
Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
DEPLOY_DIR_IMAGE has been replaced by IMGDEPLOYDIR for most use cases
since OE-Core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02. Document
IMGDEPLOYDIR and add a note to DEPLOY_DIR_IMAGE about it.
(From yocto-docs rev: dad7046f9428bde476d2241209c118d52529bed5)
Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
DEPLOY_DIR_IMAGE has been replaced by IMGDEPLOYDIR for most use cases
since OE-Core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02. Update
examples given in the documentation to use IMGDEPLOYDIR and match their
implementation.
(From yocto-docs rev: 6cad5984306ffbf748a888cedc1a5015105e89fa)
Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes the reference manual much lighter by moving
the migration guides to a separate document.
The migration guides are also reordered from last to first,
and they appear directly in the left bar, making them easier
to find in the documentation.
(From yocto-docs rev: 5121b86ee97eb62a0c69c9ad1fc0e3fabbe3e934)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-W is for turning warnings into errors, --keep-going to make sure the
whole documentation is built and all warnings will be printed before
failing.
Since there's currently no warning, it's time to introduce it!
(From yocto-docs rev: 5d7b8547549b2203a03df617cdba70ccf2194c62)
Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The routine do_sizecheck() was historically needed by legacy
devices with limited flash memory.
The lowest extreme is probably with Zaurus collie having exactly
1024*1024 = 1048576 bytes for the kernel partition.
In the years the KERNEL_IMAGE_MAXSIZE has been converted to kilobytes
thus rounded so we have now KERNEL_IMAGE_MAXSIZE_collie = "1024".
The effect is that now the check fails because we hit curiously this
| WARNING: This kernel zImage (size=1024(K) > 1024(K)) is too big for...
even though zImage is 1047288 bytes (kernel + kexecboot-klibc-initramfs).
Fix this case using test -gt (greater) instead of -ge (greater or equal).
(From OE-Core rev: 254ca956d63b4ce6aa294213b60bb943f9f3a9e6)
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was a ad-hoc solution which did not really work in all cases, now
gcompat is provided to deal with glibc based prebuilts, therefore there
is no need to provide this package
(From OE-Core rev: e2d54f02bcde7a95235a61b9622c584a77c4e9bc)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a compat library which helps running pre-compiled binaries which were
compiled for glibc but needs to run on musl systems, this is quite
common case where pre-existing binaries are supplied and can not be
recompiled immediately
(From OE-Core rev: 5efe7c06c8555672b535adae587596f65bff4fc5)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-fdtdump-Fix-gcc11-warning.patch
removed since it is included in 1.6.1
(From OE-Core rev: 23ef5cad6274604113d651da8156c96ad647dceb)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fix below error:
/include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
31 | #error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
(From OE-Core rev: f6dd68994bfd602d60aea10df42176a5d71712d7)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Helps in running tests a bit faster
(From OE-Core rev: 735799a66e52ced9de9431ad3062b13583e3754f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During do_testimage, if the target is not started within a certain
timeout, TEST_QEMUBOOT_TIMEOUT, host data is dumped to files for
each command in
${TMPDIR}/log/runtime-hostdump/<datetime>_qemu/host_<seq>_<command>.
Display the first 20 lines of top output and the last 20 lines of
bootlog to standard output for more context for the target not being
started up.
(From OE-Core rev: 441390b707bf681bc308c9ebd45ea2ae20c37d7c)
Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit removes the stack_changes ptest from aarch64 devices.
This test is buggy and fails almost 100% of the time in qemuarm64.
In general, many of the valgrind tests are more likely to fail on
qemuarm64 vs native x86_64.
This test previously worked on gatesgarth and dunfell, but has
been failing since hardknott. It might be due to a recent change
in the cross-compiler or glibc.
The test runs fine when running natively on arm on a Raspberry Pi.
Until we can find the root cause for the failures, this shorter
term solution should clear up some of the noise from the autobuilder
from a known failure.
(From OE-Core rev: 82d6411b80a46d8ec0258ca75c3c80dc6128d44e)
Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We now spend time copying the VM image into a tmpfs and with IO load on the
system, the time + the boot time of the VM can take longer than 120s. Increase
the timeout to match the added overhead of copying the image file.
(From OE-Core rev: a40087c966af5ffb9309e1ddfdb3d06973e0bddd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
