[YOCTO #14975]
rust files are not linking on target due to missing dependencies and observed below error.
error: linker `x86_64-poky-linux-gcc` not found
Added the required dependencies to run rust on target machine.
(From OE-Core rev: bb781f452299cfa6ec7fffd215b0af3149178f32)
Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is searched before
DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
DT_RUNPATH, this order ensures that injecting
malicious shared objects is way harder with DT_RUNPATH.
This is now default on major linux distributions already
(From OE-Core rev: 66f8a745668a067d8d763fa2af3e65f26c9c1ebe)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Error: Transaction test error:
file /usr/bin/vala-gen-introspect-0.56 conflicts between attempted installs of lib32-vala-0.56.3-r0.armv7ahf_neon and vala-0.56.3-r0.aarch64
file /usr/bin/vapigen-wrapper conflicts between attempted installs
of lib32-vala-0.56.3-r0.armv7ahf_neon and vala-0.56.3-r0.aarch64
The differences of vala-gen-introspect-0.56 are as follows:
@@ -2,7 +2,7 @@
prefix=/usr
exec_prefix=/usr
-libdir=/usr/lib64
+libdir=/usr/lib
pkglibdir=${libdir}/vala-0.56
if [ $# -ne 2 ]
The wrapper isn't used on target so we can simply delete it.
(From OE-Core rev: 3cf894b8a9c4fa14fcc7c7445e85e9ae3192b398)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pull in:
pseudo_util.c: Open file with O_CLOEXEC to avoid fd leak
Use close-on-exec (O_CLOEXEC) flag when open log file to
make sure its file descriptor is not leaked to parent
process on fork/exec.
Fixes [YOCTO #13311]
(From OE-Core rev: 3ec9ca0b39c9e09c5a8c8cf94e57091d1b67c9f0)
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When running the configure check "checking for ELF support in BFD", LDFLAGS
were not being passed in to libtool. In OE/YP, we need these flags when using
uninative due to the games we play with the dynamic loader.
If a version of libzstd was built against a newer glibc, it would need
newer pthread symbols which it wouldn't find with the system linker. At
runtime this isn't an issue as it would be switched to use uninative but we
pass flags in LDFLAGS to allow this.
The bug is rare to reproduce as it depends on the host libzstd was built
against.
(From OE-Core rev: 74077e10e2212349493ecfa8e7d9ca844366331f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
Fixed a bug where the content type header was not properly encoded for PKCS7
signatures when using the Text option and SMIME encoding.
(From OE-Core rev: 1fb6b8839fa7fd38595b6f3218a9b096c246b00b)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
ax_have_qt: bump serial number
Merge pull request #262 from bastien-roucaries/fromdebian20200930
Fix AX_HAVE_QT
ax_have_qt: bump serial number
Merge pull request #266 from netfab/fix-ax_have_qt
AX_HAVE_QT: remove qmake stash file before rmdir
ax_python_devel: bump serial number
Merge pull request #267 from bastien-roucaries/fromdebian20221118
Fix ax_python_devel serial 32 fails with current python3
ax_add_fortify_source: fix formatting
ax_check_sign: bump serial number
ax_cxx_compile_stdcxx: bump serial number
ax_c_restrict: fix formatting
Merge pull request #268 from omoerbeek/master
ax_check_sign: Avoid an unused warning
Merge pull request #269 from rurban/fortify3
AX_ADD_FORTIFY_SOURCE: add -D_FORTIFY_SOURCE=3 check
Merge pull request #270 from rurban/swig
fix SWIG_LIB windows newline
Merge pull request #271 from rurban/restrict
Add ax_c_restrict
Merge pull request #272 from ojwb/fix-AX_CXX_COMPILE_STDCXX-for-MSVC-C++17
AX_CXX_COMPILE_STDCXX: Fix MSVC with C++17 or later
Merge pull request #264 from thesamesam/clang-16
Clang 16 fixes
(From OE-Core rev: 4aa95afd64ce3cd4caba6f68d6b8aeeea606138a)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
From an SDK, running a meson setup build without an explicit setup
command can result in a native build when a cross build is expected.
The problem is in meson-wrapper where it tries to detect whether a
setup command is being used. The logic looks through all arguments for
a command, and the first argument it finds that doesn't start with a -
is treated as the command. This doesn't work for an implicit setup
command if any option with a space-separated argument exists. In this
case, the argument is incorrectly selected as the command, causing the
setup command options for the cross build to be excluded from the
command line, and thus a native build.
Improve the logic by just looking at the first argument. If it is
a known comand, then record it. Otherwise just assume it is the
implicit setup command.
Note that this fix does not address the possibility of a new meson
command. Two new echo statements are included to help the user in case
of trouble:
```
~/git/weston-imx$ meson --warnlevel 3 --prefix=/usr -Ddoc=false -Dbackend-drm-screencast-vaapi=false -Dcolor-management-lcms=false -Dpipewire=false -Dbackend-x11=false -Dxwayland=true -Dsimple-clients=all -Dbackend-wayland=false -Dbackend-default=drm -Dbackend-rdp=false -Dtest-junit-xml=false -Dlauncher-libseat=false -Dimage-jpeg=false -Dimage-webp=false -Drenderer-g2d=true build
meson-wrapper: Implicit setup command assumed
meson-wrapper: Running meson with setup options: " --cross-file=/opt/fsl-imx-internal-xwayland/6.1-langdale/sysroots/x86_64-pokysdk-linux/usr/share/meson/aarch64-poky-linux-meson.cross --native-file=/opt/fsl-imx-internal-xwayland/6.1-langdale/sysroots/x86_64-pokysdk-linux/usr/share/meson/meson.native "
The Meson build system
Version: 0.63.3
```
(From OE-Core rev: 9338bd66a3c9ab5cb781f2ee588306c5b31a3cb5)
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream docs currently have a typo showing the changes as 8.14.0
89d58c2ec0
9.1.0
-----
* New functions
- iter_index() (from the Python itertools docs)
- transpose() (from the Python itertools docs)
- matmul() (from the Python itertools docs)
- factor() (from the Python itertools docs)
- gray_product() (thanks to haukex)
* Changes to existing functions
- sieve() was updated to match the Python itertools docs
- maxsplit() was updated to fix a bug (thanks to abingham)
- sliced() had its type hint updated (thanks to ad-chaos)
* Other changes
- The batched function is marked as deprecated and will be removed in a
future major release. For Python 3.12 and above, use itertools.batched
instead. (thanks to neutrinoceros)
- The type hints now used postponed evaluation of annotations from PEP 563
(thanks to Isira-Seneviratne)
- Some documentation issues were fixed (thanks to Voskov and jdkandersson)
(From OE-Core rev: 436b92846406273fb3651f4f026e9fd3871ee71c)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tests need to run as a non-root user, but that user also needs to be
able to write into the tests directory to create the work directories.
Use the new ptest user that ptest-runner creates to avoid having to add
a new user, and ensure that the test/ directory is owned by the ptest
group and that group has write access.
This solves the ptest regression where since oe-core 9a287b4 no quilt
tests were actually running.
A better solution would be to allow the tests to create a work directory
in another directory, but that would need work upstream which can happen
later.
(From OE-Core rev: 70dc9c114283cde18771287fb17fcebc537e7387)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch changes the docbook-xml distribution package source from
debian to docbook which aligns the recipe with the source
originator. Other changes made to the recipe include:
This patch resolves [YOCTO #13270].
- removal of version 4.0 given docbook no longer distributes version
4.0
- simplification of the header description.
- inline comments to communicate the rationale behind gathering
multiple versions and LICENSE file handling.
- minor ordering changes to align with styling conventions and better
context to better communicate use
- Added comment about magic XMLCATALOGS variable. This variable and
subsequent inherit might be better placed in recipes that depend on
docbook-xml but leave it for now to not cause a patch landslide.
- Modify the related docbook-xml patch to remove docbook-xml-4.0 since
it is no longer provided.
- Put BBCLASSEXTEND to end of recipe per RP note on convention
(From OE-Core rev: fc4471019313d981f0c951220cc65e8374a7e8e6)
Signed-off-by: Richard Elberger <rich@richelberger.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
=========
Added experimental support for suppressing subtest output dots in non-verbose
mode with --no-subtests-shortletter -- this allows the native pytest column
calculations to not be disrupted and minimizes unneeded output for large CI systems.
(From OE-Core rev: 486c627d6851079c49e18d56d7052d3842af3206)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
============
Features
--------
- Ignore PIP_REQUIRE_VIRTUALENV for "pip index"
- Implement "--break-system-packages" to permit installing packages into
"EXTERNALLY-MANAGED" Python installations.
Bug Fixes
---------
- Improve handling of isolated build environments on platforms that
customize the Python's installation schemes, such as Debian and
Homebrew.
- Do not crash in presence of misformatted hash field in "direct_url.json".
(From OE-Core rev: 2cab887da4618a23c1fc52d27e1061102857f470)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that we have the dependencies we can set the RDEPENDS for all builds,
not just target.
(From OE-Core rev: e7980308d78e7fb8ea1568b80363c809c91c2363)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add patch to fix typo for build on musl
GDB 13.1 includes the following changes and enhancements:
* Support for the following new targets has been added in both
GDB and GDBserver:
** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
** GNU/Linux/CSKY (gdbserver) csky*-*linux*
* The Windows native target now supports target async.
* FreeBSD:
** Arm and AArch64: Support for Thread Local Storage (TLS) variables
** Hardware watchpoint support on AArch64 FreeBSD
* Floating-point support has now been added on LoongArch GNU/Linux.
* New commands:
** set print nibbles [on|off]
show print nibbles
This controls whether the 'print/t' command will display binary values
in groups of four bits, known as "nibbles". The default is 'off'.
** Various styling-related commands. See the gdb/NEWS file for more
details (see link at the bottom).
** Various maintenance commands. These are normally aimed at GDB
experts or developers. See the gdb/NEWS file for more details
(see link at the bottom).
* Python API improvements:
** New Python API for instruction disassembly.
The new attribute 'locations' of gdb.Breakpoint returns a list of
gdb.BreakpointLocation objects specifying the locations where the
breakpoint is inserted into the debuggee.
** New Python type gdb.BreakpointLocation.
** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
that formats ADDRESS as 'address <symbol+offset>'
** New function gdb.current_language that returns the name of the
current language. Unlike gdb.parameter('language'), this will
never return 'auto'.
** New function gdb.print_options that returns a dictionary of the
prevailing print options, in the form accepted by gdb.Value.format_string.
** New method gdb.Frame.language that returns the name of the
frame's language.
** gdb.Value.format_string now uses the format provided by 'print',
if it is called during a 'print' or other similar operation.
** gdb.Value.format_string now accepts the 'summary' keyword. This
can be used to request a shorter representation of a value, the
way that 'set print frame-arguments scalars' does.
** The gdb.register_window_type method now restricts the set of
acceptable window names. The first character of a window's name
must start with a character in the set [a-zA-Z], every subsequent
character of a window's name must be in the set [-_.a-zA-Z0-9].
* GDB/MI changes:
** MI version 1 is deprecated, and will be removed in GDB 14.
** The async record stating the stopped reason 'breakpoint-hit' now
contains an optional field locno.
* Miscellaneous improvements:
** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.
** New convenience variable $_inferior_thread_count contains the number
of live threads in the current inferior.
** New convenience variables $_hit_bpnum and $_hit_locno, set to
the breakpoint number and the breakpoint location number of
the breakpoint last hit.
** The "info breakpoints" now displays enabled breakpoint locations
of disabled breakpoints as in the "y-" state.
** The format of 'disassemble /r' and 'record instruction-history /r'
has changed to match the layout of GNU objdump when disassembling.
A new format "/b" has been introduce to provide the old behavior
of "/r".
** The TUI no longer styles the source and assembly code highlighted
by the current position indicator by default. You can however
re-enable styling using the new "set style tui-current-position"
command.
** It is now possible to use the "document" command to document
user-defined commands.
** Support for memory tag data for AArch64 MTE.
* Support Removal notices:
** DBX mode has been removed.
** Support for building against Python version 2 has been removed.
It is now only possible to build GDB against Python 3.
** Support for the following commands has been removed:
set debug aix-solib on|off
show debug aix-solib
set debug solib-frv on|off
show debug solib-frv
Use the "set/show debug solib" commands instead.
For a complete list and more details on each item, please see the gdb/NEWS
file, available at [1]:
[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-13.1-release
(From OE-Core rev: 87a8c2af735e06338463414a2cbcd3224b9ea112)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building native qemu with 6.2 kernel headers, qemu fails to build:
In file included from /usr/include/linux/btrfs.h:29,
from ../qemu-7.2.0/linux-user/syscall.c:165:
/usr/include/linux/fs.h:50:8: error: redefinition of ‘struct file_clone_range’
50 | struct file_clone_range {
| ^~~~~~~~~~~~~~~~
../qemu-7.2.0/linux-user/syscall.c:129:8: note: originally defined here
129 | struct file_clone_range {
| ^~~~~~~~~~~~~~~~
Backport changes to linux-user that remove the local copy of struct
file_clone_range.
Patches from https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berrange@redhat.com/
(From OE-Core rev: 65b1e199dcaabf93bae33e06727bb1238b703d83)
Signed-off-by: Joel Stanley <joel@jms.id.au>
Tested-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently binutils in buildtools is searching for /etc/etc/ld.so.conf
which makes no sense. ld_sysconfdir already contains /etc so we need to
drop the /etc from the fixed string.
(From OE-Core rev: ccd28c418ab8390118d738fbe914395b5c2a1f75)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There's no need to use the internal glib fork for nativesdk builds, as
we can use the proper nativsdk-glib-2.0 recipe.
This means we're shipping less statically linked and obsolete code, and
can also drop two patches to that code which were only needed in
nativesdk builds on Windows.
(From OE-Core rev: f893b70a2db326e82f1de5c47b7da3855fa42439)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
