Age | Commit message (Collapse) | Author |
|
This adds the armv8a tuning for Cortex-A32, Cortex-A35, Cortex-A53 and
Cortex-A72. This matches the other ARM tunes.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
|
|
Tune files that inherit the arch definitions already define
appropriate -mcpu options, which are equivalent of the correct -march
and -mtune combinations. This is preferred since gcc is getting
stricter and stricter with option check semantics and can now find
incompatible -march and -mcpu options better with every release. It
does an internal feature consistency check and if it finds any
discrepancies between what -mcpu would expand to as compared to
-march, it will flag the options to be incompatible. For the naked eye
it looks wrong, but gcc will translate -mcpu to a given -march
internally and it might not match what we set in these arch files.
The effects are quite subtle, where this can result in configure tests
failing to compile due to these incompatible options and a feature
option getting disabled for a recipe for no reason.
E.g., with GCC 9, which can now detect that -mcpu=cortex-a5 and
-march=armv7-a are incompatible, many features in libstdc++ end up
disabled due to configure check failures, e.g., size_t size, ptrdiff_t
sizes, which in turn results in compiling libstdc++ with wanted
features disabled.
This is an alternative solution to the same problem originally
implemented by Khem Raj in commit ac83d22e, but this time only
affecting -mcpu and -march options without other side effects.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
|
|
This reverts commit ac83d22eb5031f7fdd09d34a1a46d92fd3e39a3c.
This solution had unforeseen side effects, which, e.g., lead to the
following sanity error if trying to build with the arm926ejs default
tune:
Error, the PACKAGE_ARCHS variable (all any noarch arm armv4 armv4t
armv5 armv5t armv5e armv5te arm926ejste arm926ejse <BSP name
withheld>) for DEFAULTTUNE (arm926ejs) does not contain
TUNE_PKGARCH (arm926ejst).
An alternative solution will follow, which only affects the -mcpu and
-march options without other side effects.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
|
|
This reverts commit 1d6d5bb30a83f9136b7c33e297d48564ae61b50e.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
|
|
libxml-native by default uses a XML catalogue at /etc/xml/catalog, instead of
the one in the sysroot. Until this is fixed (#13260) override the XML catalogue
manually in the recipe to point explicitly at the docbook-xml and docbook-xsl
catalogues.
This fixes either complete build failures (where the host doesn't have
docbook-xml installed) or slow builds (where the host doesn't have docbook-xsl
installed).
(From OE-Core rev: efb6168e41797ad6ed00ede6f3d9141b90eff4b5)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From meta-yocto rev: 476f2fd598c12bfee7d2aeddbe72a360826f249c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Boot test for all these boards.
(From meta-yocto rev: 135958cd17531fd5eeb5e1eff3e673c435def1b2)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
On some hosts the wic.Wic2.test_wic_cp_ext selftest was failing as files weren't
being copied into the rootfs with "wic cp". This was due to a bug added by:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=89d4a8df074598cfb3a76e41db7c45d845afd961
where there should be a second newline added at the end of the expression due
to the difference in the way echo -e and printf behave.
[YOCTO #13237]
(From OE-Core rev: 2f3adb21cc5067458a12964d0bde235966a20a60)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This makes sure, e.g., ${SOC_FAMILY} and ${MACHINE} have higher
priorities than aarch64.
(From OE-Core rev: 4d1339af88543d85930139dbcb87a669f285ea66)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Platforms like powerpc64le have different variants of the same target.
Perl guesses that the target should be called powerpc64le-linux, while
TARGET_ARCH think it is called ppc64le-linux. If we use TARGET_ARCH
for perl-native on powerpc64le this build will fail since the
post-install rm command won't reference and existing file.
We know that there is only one arch existing per build, so use a
wildcard for finding the path instead of trying to guess the correct
architecture name.
(From OE-Core rev: 6eadd9f5ac2887311ae9ed133b389ae4d64a8181)
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The armv8a tune specific PACKAGE_EXTRA_ARCHS contained tune feature
names like "crc" and "crypto" rather than package architecture names
like "armv8a-crc" and "armv8a-crypto".
(From OE-Core rev: 1756f2354745ee709886683422887efed4e10dba)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
fix below link error for powerpc
lib/libLLVMSupport.a(CommandLine.cpp.o): in function `llvm::cl::opt_storage<(anonymous namespace):
:HelpPrinterWrapper, true, true>::setLocation(llvm::cl::Option&, (anonymous namespace)::HelpPrinterWrapper&) [clone .isra.189]':
/usr/src/debug/llvm/8.0-r0/git/llvm/include/llvm/Support/CommandLine.h:1218:(.text.startup+0x5c):
relocation truncated to fit: R_PPC_PLTREL24 against symbol `llvm::errs()' defined in .text section in lib/libLLVMSupport.a(raw_ostream.cpp.o)+8000
lib/libLLVMSupport.a(CommandLine.cpp.o): in function `setLocation':
(From OE-Core rev: 5302047be6bcdae85a43f9b09778a91dcd03b191)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Current validation check function inside resulttool disallow the
report for single result file although the underlying library
was able to handle both directory and file as source input to report.
Removed the validation check as it was no longer needed and to
enable report for single result file.
(From OE-Core rev: a85a8febf04d763dd5b3d20487d528731105afab)
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Use the default POSIX sh instead of relying of var-SHELL being set to a
compatible shell. Such that in cases where SHELL is set to a
incompatible shell (e.g. csh, zsh, fish, etc.) the terminal command does
not just silently fail.
(From OE-Core rev: 50d3ec1ac994fb5968d8edf82823a7e3d1d67d21)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This changes the runfile that is generated to have the same behaviour as
bitbake with regards to emitting the shebang and trap code. The existing
implementation used 'env' with the current var-SHELL. This means that if
the user has configured there system/environment with a alternate shell
(e.g. csh, zsh, fish, etc.) the do_terminal function would attempt to
execute with the wrong/incompatible shell and fail silently.
With this change devshell and other classes that rely on terminal can
now run when the var-SHELL is not set to a sh compatible shell. For
devshell, it will launch the devshell with the users configured shell.
(From OE-Core rev: 53724281eb486847bc3be824aa4513a8688ec296)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
webkitgtk 2.22.7 is a bug fix release in the stable 2.22 series.
* Fix rendering of glyphs in Hebrew (and possibly other languages) when
Unicode NFC normalization is used.
* Fix several crashes and race conditions.
See https://www.webkitgtk.org/2019/03/01/webkitgtk2.22.7-released.html
(From OE-Core rev: 0ee8d4d58b2d755615ae4f7c3783b72d5aabaa63)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Backport patch to fix CVE-2017-6519.
CVE: CVE-2017-6519
(From OE-Core rev: 979e3f4ac1e12228d368315169a32d5ab0209e91)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Move prepare_recipe_sysroot's task dependency on populate_sysroot from
base.bbclass (where it was specified in the middle of do_configure's
definition) to staging.bbclass (where the rest of
do_prepare_recipe_sysroot is defined). This was a left-over from when
recipe specific sysroots were introduced in commit 809746f5 and the
task dependency on populate_sysroot was moved from do_configure to
do_prepare_recipe_sysroot.
(From OE-Core rev: fe6d020dd609fbde7e4413cef9bbdd4e3962c82c)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
tzdata is converted to an empty meta package which pulls in all
subpackages. The subpackages are defined in a TZ_PACKAGES variable so
that we don't have to repeat ourselves.
The timezones and conffiles which were in the tzdata package are moved
to a new 'tzdata-core' package.
(From OE-Core rev: 2af4d6eb2526d60b26bc5128068541ff3350fb58)
Signed-off-by: Paul Barker <paul@betafive.co.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From meta-yocto rev: 85ed7ed9d3b34562b1df30e67aa0698facdb0dd5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 13e45fffb66c7cb7ba0d07bed063c0c5ce57004b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Currently CONFIG_RFKILL is enabled only if both bluetooth *and* wifi
distro features are present. It should be enabled when either feature
is present. Fix this by switching to use of bb.utils.contains_any().
(From OE-Core rev: 5e6d7760c599b09b9417aa8d044084f4c5123762)
Signed-off-by: Matt Porter <mporter@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add missing runtime dependencies: the test suite needs proper chmod from
coreutils, and the Europe/Minsk timezone.
Also change run-ptest to use -W (run verbosely on failure) instead of -v (always
verbose) to hopefully reduce the noise in the ptest reports.
(From OE-Core rev: 7574f6850797fb7556d2f8077860b7c1d26ae8ec)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
If kernel-devsrc is used in a SDK context, the symlink from usr/src/kernel
points to an absolute path '/lib/modules/${KERNEL_VERSION}/build',
which ends up pointing to the local machine's build directory.
To address this issue change the symlink to be realtive to
${D}/lib/modules/${KERNEL_VERSION}/build.
(From OE-Core rev: 95bc738e7f10d492f5db33fc581e9796e52a9d3f)
Signed-off-by: Henrik Nymann Jensen <hnje@triax.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Backport a patch from upstream to use GNUInstallDirs instead of hand-coded path
logic, so we have proper control over where files end up.
(From OE-Core rev: 7c7d8ce6fe54e239374a6a04c007b4aa0712ba33)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
adwaita-icon-theme uses gtk-encode-symbolic-svg to generate icons, so DEPEND on
librsvg-native (and gtk+3-native, via gtk-icon-cache.bbclass) so that this tool
exists and can load SVG files.
(From OE-Core rev: f109bb56f48103a7a2b9f77af72e860c6e994b2b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This was added so that adwaita-icon-theme can find the SVG loader for icon
generation, but the fix is in the wrong place. GTK+ does not depend on librsvg
at all, the tool in GTK+ which loads the icons uses gdk-pixbuf which uses
loadable modules.
This reverts commit 66828ff04d107b7719c9c8857d7c6c2ebf20a8bb.
(From OE-Core rev: 57c112338068b6e8582480b50b025590fef51052)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Beautify the machine config files by making the names and descriptions
more uniform and verbose
(From meta-yocto rev: 159a8c9080af125c657558b4789f4aa8410e4fa2)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
new SRCREV
If the system had previously fetched a source repository for use by gitsm,
and then the SRCREV was updated and the new commit already existed, the system
would not re-evaluate the submodules and update them accordingly.
The cause of this issue was that need_update was being used, unmodified, from
the base git fetcher. It did not have any knowledge, nor did it care if we
were moving commits and needed to re-evaluate what was happening due to this
switch.
To fix the issue, during the download process we add all processed (by
gitsm) srcrevs to the git config file, as bitbake.srcrev. This allows us to
use a new need_update function that not only checks if the git commit is
present, but if we have previously processed this commit to ensure all of the
submodule components are also present.
This approach is used, instead of iterating over the submodules in need_update
to avoid a potential race condition that has affected us in the past. The
need_update is called only with the parent locking. Any time we need to dive
into the submodules, we need to lock, and unlock them, at each stage. This
opens the possibility of errors in either the code, or unintended race
conditions with rm_work.
This issue was discovered by William A. Kennington III <wak@google.com>. The
included test case was also written by him, and included unmodified.
(Bitbake rev: 30fe86d22c239afa75168cc5eb262b880886ef8a)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
lzip is pretty niche: people are typically either sticking with that they know
(gzip, bzip) or using xz. Data point: only one recipe in oe-core is shipped as
a .lz file.
(From OE-Core rev: 80b0ac3bdbaee50d0023b7c869dd204485903dfe)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
So that it says '8.0.0' to reflect the recent PV change.
(From OE-Core rev: 3b4049157a72bcd984f93405a75946a39c045f2d)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
PV is 2.32.0 even though the actual release upstream is 2.32. To a human this
is insignificant, but to automated tooling it matters. Specifically,
cve-check-tool can't identify CVEs that are in 2.32.
Set CVE_VERSION for now, which should be removed when PV and the upstream
version match again.
(From OE-Core rev: 487c8356c22deb29867baf3da74f6d86502d5b3b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: e61c42ee49029ae8ffec58128dd083031305d9e5)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 8995f2c7d6f2f6f760811976af77e949d505a5d8)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 4ec161ea684b305b303f32e96ce23f472c82e1a1)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Beautify the machine config files by making the names and descriptions
more uniform and verbose
(From OE-Core rev: 1108a24e2c58794163c8cf35154f8be5c1d06c29)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
LLVM is now warning if your host compiler is gcc <5.1, and some of our supported
operating systems still only have 4.8.5. Set
LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN so those builds continue to work, hopefully
we retire the old operating systems before LLVM requires 5.1+.
(From OE-Core rev: 0e7d761b1360f603a4cc0de15c67f4e182e5a6a4)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Also, update PV to match the version scheme used by upstream
to tag releases (e.g. major.minor.patch).
(From OE-Core rev: 4405a1793a42aecd7923ab2b18df296ed8c32dc1)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
x.0.0 releases are actually considered 'development' by the upstream,
and true releases are x.0.1:
https://www.mesa3d.org/relnotes/19.0.0.html
(From OE-Core rev: ceb6a4373dd68cc65dd3d2d73cf632bc34dfbeb0)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The riscv GLIBC_DYNAMIC_LINKER changes were dropped during the gcc 8.3
update, breaking usrmerge support.
(From OE-Core rev: 299ec755de5d568f284d98c77863da4636e3fd05)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The copyright date changed in the license file, thus the hash change.
CMake 3.14 fixes some issues with implicit include path that lead to
errors with gcc not finding "stdlib.h" etc in include_next.
(From OE-Core rev: ec2764aa4957b802ed2612dd7633aed5b941bfb0)
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 7e29e7cb13ed13a7049328cd2169cd515b630fc3)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: cf7473fae0f339286221f8e2b54d5c38ea41e6e2)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There's a sort-of-official port of asciidoc to Python 3. Whilst the official
replacement is asciidoctor which is rewritten in Ruby, this is a fairly trivial
swap and removes Python 2 from core-image-sato builds entirely.
Moving forward we should evaluate asciidoctor, but that can wait.
Change the RDEPENDS so that python3 is only a dependency for target and
nativesdk builds, for native this can use the host python3.
Remove redundant DESTDIR export that isn't needed.
(From OE-Core rev: 266a13139ea45e28deb167f077917f04c3bdb7e6)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 037b544431076b94e85281c7deb527a44a600f5a)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 9bcfb1061c80fe51e47e102d6ad4c0d96392b90e)
Signed-off-by: Vincent Prince <vincent.prince.fr@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
libpcre2 is needed to enable grep option to journalctl.
(From OE-Core rev: 623946c9b56d4a253e0e82936ec86595edc1da1b)
Signed-off-by: Vincent Prince <vincent.prince.fr@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This doesn't appear to be required at all.
(From OE-Core rev: d8269db061c471d230dfd27e158f1aa5ce188e5a)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
LLVM doesn't actually need pythonnative, the host Python2 is sufficient but
cmake's executable searching currently isn't reliable in cross-compilations.
Convince cmake by setting PYTHON_EXECUTABLE to point at python2 in the HOSTTOOLS
directory. Note that currently LLVM *needs* python2 currently:
https://github.com/llvm-mirror/llvm/blob/master/CMakeLists.txt#L670
(From OE-Core rev: 1587475e45edc995b7643844594abc94160a5549)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: f21aaefb6f082768d4bc5c55fc59a9142cfcc2d3)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|