Install dpkg-perl scripts to versioned perl directory, otherwise the
following traceback happens when running, e.g. dpkg-architecture on the
target:
Can't locate Dpkg.pm in @INC (you may need to install the Dpkg module)
(@INC contains: /usr/lib/perl5/site_perl/5.30.1/aarch64-linux
/usr/lib/perl5/site_perl/5.30.1
/usr/lib/perl5/vendor_perl/5.30.1/aarch64-linux
/usr/lib/perl5/vendor_perl/5.30.1
/usr/lib/perl5/5.30.1/aarch64-linux
/usr/lib/perl5/5.30.1 .) at /usr/bin/dpkg-architecture line 25.
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: bdd4757ae057c7b3bfe27353fa25c4d7807a86ce)
Signed-off-by: Manuel Leonhardt <mleonhardt@arri.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Our patched python3-config uses distutils, but that will emit a
DeprecationWarning when imported. This isn't useful when using the
output of python3-config to find include paths.
This isn't a huge problem typically as the warning goes to stderr, but
some build systems read both stdout and stderr.
(From OE-Core rev: e25b8f5af70a094307dc5c0a25f213ae9570f349)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
/var/log is normally a link to /var/volatile/log and /var/volatile is a
tmpfs mount. So anything created in /var/log will not be available when
the tmpfs is mounted.
Also some whitespace clean up.
(From OE-Core rev: 876d09bd42e24db3a498148e3305fb27f70ceda0)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since the following commit, package_qa_add_message is no longer
available, use oe.qa.add_message instead.
"""
commit f0ad152ef4cc15c042bc9eeefb6af096d054b220
Author: Mike Crowe <mac@mcrowe.com>
Date: Fri Oct 15 15:39:53 2021 +0100
lib/oe/qa,insane: Move extra error handling functions to library
Extract package_qa_write_error, package_qa_handle_error and
package_qa_add_message functions from insane.bbclass to lib/oe/qa.py and
drop the package_qa_ prefixes.
...
"""
(From OE-Core rev: d181f8c3798165808b1f529650ca47aae7730d9d)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Handle github protocol changes not covered by the script due to variable indirection.
(From OE-Core rev: 3bb1cb476dbad1037522970af9afd69691a7033c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The libgfortran configure sets FC to be $GFORTRAN. We did used to patch
that out but rather than carry a patch to gcc, just set GFORTRAN as
needed.
(From OE-Core rev: 4ec096a9ce8a49b631efc50e7d95ff653d4c4374)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add fcntl64 wrapper which hopefully fixes issues seen in findutils and the find
command in the libtool removal code when built with LFS compile flags on Gentoo.
(From OE-Core rev: f26867fe4daec7299f59a82ae4a0d70cceb3e082)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As far as I can see, when building libgfortran we don't set GFORTRAN so this
patch does nothing any more. The fortran build and gcc recipes have changed
massively since gcc 4.2.2 so I think this patch is simply obsolete.
I did test building libgfortran with and without this patch and there was
no difference, the correct fortran compiler is found. If it were an issue
we should just set GFORTRAN correctly. Therefore drop the patch.
(From OE-Core rev: bc5209aa5f07cea00416852532b90aba044defd5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is uncertainty about the default branch name in git going forward.
To try and cover the different possible outcomes, add branch names to all
git:// and gitsm:// SRC_URI entries.
This update was made with the script added to contrib in this patch which
aims to help others convert other layers.
(From OE-Core rev: b51c405faf6f8c0365f7533bfaf470d79152a463)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch has headers as if it were submitted upstream but I can't find any
record of it. I did try tests with it removed, building the referenced testsuite
files with -Werror and it all works just fine with no warnings or errors (tested
on MACHINE=qemux86). I suspect this was fixed in gcc itself in other ways.
As such I think this patch isn't needed and suggest we drop it. If there is
a reason it is needed, please report along with an example of how to reproduce
issues.
(From OE-Core rev: d83e12da74b853ae33045e5c216c90c78a19f54d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I took 5 of our patches and submitted to upstream gcc. This highlighted that
patches 0026 and 0018 should be merged together and some tweaks were made to
try and make it acceptable to upstream. The other patches have their headers
updated to match what was submitted.
The libstdc++ option patch was also cleaned up ready for upstream as the
documentation wasn't quite right.
The CXXFLAGS_FOR_BUILD piece of 0026 is separated out into a new patch which
can be submitted separately to upstream.
Two of the patches have been merged, status updated accordinly.
(From OE-Core rev: df9b8ec56ff29f14feb1fde6acbdf9c4667430cf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meson 0.60 turns unknown options into them hard errors, so instead of relying on g-i class
(where the options are mandatory) add g-i dependencies explicitly.
(From OE-Core rev: 9c0cc06a3d857124c0e1c1c9342f79ba5a3b10bc)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the same solution that has been applied to meson.bbclass to
allow building with meson after it has been updated to a new
version. It needs to be applied here as well since qemu uses meson
without inheriting meson.bbclass.
(From OE-Core rev: 9d05227e910d3f374ba7a9763ff2584b9e40db61)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without a native environment file, find_program() can't
locate the native program inside SDK.
That stops wayland compositor using wayland scanner.
(From OE-Core rev: c6aed1084006727e3baf70ab9d1f70d9d2d6c01f)
Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After meson 0.56.0, <lang>_args and <lang>_link_args would be
regarded as meson built-in options.
(From OE-Core rev: 50c8f654e9006a7c902dd76f75082d4f8d668d0c)
Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1.2.2
* Fixed
- Illegal characters in error messages were surrounded by two
pairs of quotation marks
* Improved
- TOMLDecodeError.__module__ is now the public import path (tomli)
instead of private import path (tomli._parser)
- Eliminated an import cycle when typing.TYPE_CHECKING is True.
This allows sphinx-autodoc-typehints to resolve type annotations.
(From OE-Core rev: ab86f496fdead3dabe8b252a6cacaeb10ce03b5a)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6.24.0 - 2021-10-23
* This patch updates our vendored list of top-level domains, which is used
by the provisional domains() strategy.
* (did you know that gTLDs can be both added and removed?)
6.23.4 - 2021-10-20
* This patch adds an error for when shapes in xps.arrays() is not passed
as either a valid shape or strategy.
6.23.3 - 2021-10-18
* This patch updates our formatting with shed.
(From OE-Core rev: b7d90cf4fe2a021e8709a64bcae285ec81eb5ed8)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch looks obsolete because it looks like part of an upstream
backport on a very old gcc version (4.3.3) and looks incomplete. The
diff also has little context making it likely to be a rebase error.
Builds seem find without it so drop it.
(From OE-Core rev: 7bc50b6de2df8555f7e19ff37f103bbe65955f72)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we now have recipe specific sysroots we no longer need this patch
to avoid the dtrace headers affecting the build of gcc-runtime. Drop
the patch.
(From OE-Core rev: 9aa8ff2dbbbf38cb0c87efd32db64b8ddf485ddf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SYSTEMLIBS_DIR change was spread over three patches, merge these
together since there is no value in having them separate.
(From OE-Core rev: dd1fef1b520efaac6a21f26332c25bdcc0110c12)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I went through and cleaned up the headers/descriptions on several of the
libtool patchset and submitted (or resubmitted in some cases) them
upstream. This patch updates/renames them to match what I did.
I did fix some whitespace issues in some of the patches and also merged
one case where we had a patch of already patched code.
This makes it clear what was submitted and makes resubmission easier if
ever needed too.
(From OE-Core rev: 9bb9a4e8bd408c7a42913aa3e1ec541919b59584)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use different recipe names for the two different targets so that
when switching libcs overlapping files in the sysroot don't cause
issues.
(From OE-Core rev: 33be44a02beb7c52f075f660ad8e0641e360011c)
Signed-off-by: Pgowda <pgowda.cve@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
