| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Drop add-missing-ldflags.patch, its already applied to gdb 14
* Add dependency on mpfr for cross/cross-canadian/target recipe
* Remove gcc-only complier restriction, clang can compile it just fine
* Notable changes are here [1] [2]
[1] https://sourceware.org/git/?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=refs/heads/gdb-14-branch
[2] https://www.sourceware.org/gdb/download/ANNOUNCEMENT
(From OE-Core rev: 2a0f7255a740ffbfe5a7858ef01a3ba6cadca383)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* it was already added for target and cross-canadian gdb in:
commit 4643d1eb222151384f77d13a936537aae5ca3fe6
Author: Khem Raj <raj.khem@gmail.com>
Date: Fri Nov 5 17:37:33 2021 -0700
gdb: Add dependency on libgmp
gdb 11 has added this library as must have
* but gdb-cross.inc overwrites DEPENDS from gdb-common.inc
and needs the dependency as well as shown in log.do_compile:
checking for libgmp... no
configure: error: GMP is missing or unusable
make[1]: *** [Makefile:9418: configure-gdb] Error 1
and in gdb-cross-i686/11.1-r0/build-i686-oe-linux/gdb/config.log:
configure:10402: checking for libgmp
configure:10422: gcc -o conftest -isystem/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/include -I/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/include -L/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/lib -L/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/lib -Wl,-rpath,/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/OE/tmp-glibc/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 conftest.c -lncursesw -lm -ldl -lgmp >&5
conftest.c:52:10: fatal error: gmp.h: No such file or directory
52 | #include <gmp.h>
| ^~~~~~~
* this fails only when the host OS doesn't have GMP installed
otherwise it will use libgmp from host and ignore
--with-libgmp-prefix=/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/OE/tmp-glibc/work/x86_64-linux/gdb-cross-i686/11.1-r0/recipe-sysroot-native/usr
(From OE-Core rev: 09a7d9d8d83529d82f847e52feac7719efb02a99)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Various recipes were missing a pkgconfig inherit or pkgconfig-native
dependency despite using pkgconfig.
Add the inherit to igt-gpu-tools/gdb/libmodulemd/libwpe/xwayland/waffle
shaderc/iputils/wpebackend-fdo/lttng-ust/cargo.
(From OE-Core rev: 777d9744570c2dc119dc5d04985896bbb1da5885)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the result of automated script conversion:
scripts/contrib/convert-overrides.py <oe-core directory>
converting the metadata to use ":" as the override character instead of "_".
(From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
This allows avoiding having gdb inside the target image, which might
be too resource-constrained, or otherwise inconvenient.
(From OE-Core rev: b903f250a7bbf04d5853f537b7565a80fb7ce1f3)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"yocto-compat-layer.py --machines" showed that shared packages like
gcc-cross-powerpc64 have a sstate signature that depends on
TUNEFLAGS. As a result, there are unnecessary rebuilds and potential
conflicts in a multiconfig.
That's due to the way how TARGET_ARCH is set. Richard Purdie suggested
setting TARGET_ARCH[vardepvalue] as fix, which works. It would be
shorter to do that in cross.bbclass instead of repeating the relevant
line in different recipes, but Richard was concerned about potential
side-effects in other usages of cross.bbclass.
TARGET_GOARM as used in go.inc is still causing signature differences
for go-cross-powerpc64 and machines b4420qds-64b and p5020ds-64b. This
needs further investigation.
(From OE-Core rev: 39bfa0dd3237cbca47e7fca1075d521f9d073f25)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gdb-cross used to be specific to the tune flags, but isn't
anymore. Therefore it is enough to use TARGET_SYS instead of
TUNE_PKGARCH to create a unique path.
Fixes a sstate signature difference that was found via
yocto-compat-layer.py's test_machine_signatures check. In practice it
probably showed up as unnecessarily rebuilding gdb-cross when
switching between machines like intel-corei7-64 and qemux86-64.
(From OE-Core rev: f346473a4868563db7fb63665e808c3fe25a8b58)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Some source code of gdb is generated with flex or bison. Make both
dependencies, to avoid compilation failure on host without them.
(From OE-Core rev: ed521f12c56375de8474b0127cc8a7c25ea93e1e)
Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
This was overlooked in the move to Python 3
(From OE-Core rev: 2ec8db434c6da54333cbdc54763bb5561b6e4d10)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From OE-Core rev: 675d11c73dc1f420c471af01a520f6a20d8a7337)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUILD_SYS variables
The code that utilized them was superseded by the code (in the same patch!)
that is utilizing STAGING_LIBDIR/STAGING_INCDIR, and wasn't correct in the
first place as HOST_SYS is not necessarily the same as the sysroot directory
name.
(From OE-Core rev: 8834e81a38c24a066bb4fefa93da61011d0db244)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From OE-Core rev: 41673bb53108cd4d0f0f37c8c675256c80173135)
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
variable contents are displayed properly when debugging qt applications remotely
see [1] for further details
[1] http://qt-project.org/doc/qtcreator-2.6/creator-debugging-helpers.html#debugging-helpers-based-on-python
(From OE-Core rev: 440440363dded1d1549dc94a3eaccfcbb3cf517d)
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
| |
This allows them to co-exist together in the native sysroot, with one
set of cross tools per target architecture.
(From OE-Core rev: a2c5509520d5c3e082f55844e6545d0309565f8f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
gdb depends on readline so gdb-cross needs to depend on readline-native to
build successfully.
(From OE-Core rev: ee132d68220d7f515760d47db57e00d1d8263a1a)
Signed-off-by: Mike Crowe <mac@mcrowe.com>
Acked-by: Phil Blundell <philb@gnu.org>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GDB wants to install a bunch of files in ${datadir}/gdb/python/gdb
and ${datadir}/gdb/syscalls. These pathnames are invariant with
TARGET_ARCH which means that if you build gdb multiple times for
different targets they will all try to write to the same location
and you get a lot of warning spew about manifest conflicts.
Prevent this by factoring the target specification into ${datadir}
so that different copies of GDB install their files into different
paths.
(From OE-Core rev: 3e87aba1ee2ca0e39ba66fb7cba52e48df499c23)
Signed-off-by: Phil Blundell <philb@gnu.org>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
| |
Python isn't in DEPENDS but can be autodetected from the sysroot. Explicitly
disable it to ensure deterministic builds.
(From OE-Core rev: b8dd9592f844d15cdc8631b56ec42888a07826c9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fixes communication between gdbserver and gdb-cross
by using the same expat settings for both recipes.
* Adds missing build dependencies for expat/expat-native.
* Adds missing glibc-thread-db runtime recommendation
to gdbserver, which was set only for gdb.
(From OE-Core rev: 38ee88e3b32b7444d7f1eb64f1b4f69a48fe0458)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.
The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.
Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|