>From gdb documentation:
> There are two ways that highlighting can be done. First, if
> gdb was linked with the GNU Source Highlight library, then it
> is used. Otherwise, if gdb was configured with Python
> scripting support, and if the Python Pygments package is available,
> then it will be used.
(From OE-Core rev: b1106ed570a237f3ab80ba3fedb086c9ec0cb4a8)
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Firstly, just include xz support in all gdb configurations to simplify config.
Most systems would already have the shared library so this isn't a big problem
for a larger debugging tool.
The PACKAGECONFIG duplication is also confusing. The only PACKAGECONFIG which
needs special handking is the python one due to the differing modules needed
in the nativesdk case. Remove all the other duplicate entries which should work
through our usual class extension code.
(From OE-Core rev: d6eefdd66171c2bcdeeebc8a9b583c5383c80bf6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enabling minidebuginfo is not useful if gdb and systemd-coredump
are unable to parse it.
In order to parse it, gdb needs xz support. Systemd needs coredump enabled, as
well as elfutil enabled as well (systemd-coredump loads libdw which is part of elfutils using dlopen).
(From OE-Core rev: 0d2df803bebfd7e832ab7da54c4dacaaeeb424a9)
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
TUI mode needs terminfo at runtime, which is required to be
explicitly stated in the respective PACKAGECONFIG variable.
Without this change /etc/terminfo/ might be missing, which
leads to a runtime error when trying to use tui, e.g.:
(gdb) tui enable
Cannot enable the TUI: error opening terminal [TERM=xterm-256color]
(From OE-Core rev: 5f17bc03a0c2d894e43c3c835fa38a24b1d5df64)
Signed-off-by: Stefan Tauner <stefan.tauner@artech.at>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Depending on all of python3 (which pulls in all modules)
is not needed, python3-codecs is enough.
(From OE-Core rev: 718eda28f4f54d3033d2925e6c1232f4f8c2bc49)
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>
error message:
file /usr/share/info/sframe-spec.info conflicts between attempted installs of binutils-doc-2.40-r0.aarch64 and gdb-doc-13.1-r0.aarch64
(From OE-Core rev: 26760f6220b459a34e6cdef3cd70be40dc3b68c8)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes an arch linux gdb configure error with liblzma installed.
Without the --with-liblzma-prefix option, when configuring the target
gdb, gdb configure may find the native liblzma (on a non-multiarch
system) and try to use it, which gives a configure error. We already
use --with-libexpat-prefix for expat, we just need to do the same for
liblzma.
This was reported here:
https://github.com/sifive/meta-sifive/issues/34https://github.com/sifive/freedom-u-sdk/issues/148
(From OE-Core rev: 56623848f45cf475f909beb75209323a89837169)
Signed-off-by: Jim Wilson <jim.wilson.gcc@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gdb 11 has added this library as must have
(From OE-Core rev: 4643d1eb222151384f77d13a936537aae5ca3fe6)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Those were missed in previous rounds of automated and manual conversion.
(From OE-Core rev: 22f9c7268b542baf6cd8aa0e34c8fb7aa1579e08)
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
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>
Obtaining debug information by having it served automatically via http
is far more pleasant than messing about with debugfs and gdbserver or
transferring and installing -dbg packages by hand.
I believe we should follow the desktop distros and have it enabled
out of the box. Please see the following commit for the description
of how it works.
(From OE-Core rev: 024c88c82791a113b614abf61ffd82e097bf21d1)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added HOMEPAGE and DESCRIPTION for recipes with missing decriptions or homepage
[YOCTO #13471]
(From OE-Core rev: bb05814335e7101bfd8df0a11dc18a044e867bed)
Signed-off-by: Dorinda Bassey <dorindabassey@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
here is full announcement [1]
Do not add --disable-static, without adding --enable-shared
because certain libraries e.g. libctf expects the default
to be static which is only disabled if --enable-shared is specified
Do not limit make subdirs, this is only needed when building in a
unified tree, here builds are happening from a release tarball so it is
redundant
[1] https://www.gnu.org/software/gdb/download/ANNOUNCEMENT
(From OE-Core rev: 8fb5fe5a82d173428d96ab43bab25b89ac6f25ea)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
LTTng depends on liburcu which is not yet ported to ARC
so disable LTTng on ARC for now.
(From OE-Core rev: 701e63154c727522704aee6e890dd7d2b5615c6d)
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Allow the tui (Terminal User Interface) option to be set via a PACKAGECONFIG.
(From OE-Core rev: b4dd830e3407e1ebfbb13387fa359e356fd12ab9)
Signed-off-by: Trevor Woerner <trevor@toganlabs.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
uclibc support was removed a while ago and musl works much better. Start to
remove the various overrides and patches related to uclibc which are no longer
needed.
uclibc support in a layer would still be possible. I have strong reasons to
believe nobody is still using uclibc since patches are missing and I doubt
the metadata even parses anymore.
(From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We see:
file /usr/share/info/bfd.info conflicts between attempted installs
of gdb-doc-7.12.1-r0.core2_64 and binutils-doc-2.28-r0.core2_64
You can't really have gdb and not binutils, so there is no need
to do alternatives here ; just clobber the one from gdb and let
the binutils one be the default.
(From OE-Core rev: 19a825a578e2e705e5502982b787cff54d021359)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reduce duplication in MIPS variants now that the MACHINEOVERRIDES
variable is defined
(From OE-Core rev: 82c73101d9788c561ff9c69914b46ca8355d28fe)
Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
41d8236 Set GDB version number to 7.11.1.
136613e Fix PR gdb/19828: gdb -p <process from a container>: internal error
a0de87e Make gdb/linux-nat.c consider a waitstatus pending on the infrun side
cf2cd51 Add mi-threads-interrupt.exp test (PR 20039)
f0a8d0d Fix double prompt output after run control MI commands with mi-async on (PR 20045)
b5f0db4 Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)
7f8e34d Use target_terminal_ours_for_output in MI
(From OE-Core rev: 371345c0dc49bf781c27aea1e9f6a4c947fa30e6)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current MPX target descriptions assume that MPX is always combined
with AVX, however that's not correct. We can have machines with MPX
and without AVX; or machines with AVX and without MPX.
This patch adds new target descriptions for machines that support
both MPX and AVX, as duplicates of the existing MPX descriptions.
The following commit will remove AVX from the MPX-only descriptions.
This commit is backported from 7.12
(From OE-Core rev: dee987b6f157b0bc245086d3af914d411ae6d1ab)
Signed-off-by: bavery <brian.avery@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
when building from git we also get the binutils
components since the tree for gdb and binutils is
same, this can then casue building binutils with
gdb as well and cause packaging conflicts, hence
disable the binutils pieces in configure itself
(From OE-Core rev: d5369cf951dbc20881f4967ab679e08a95643353)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
WARNING: QA Issue: gdb rdepends on libiconv, but it isn't a build dependency? [build-deps]
We already have virtual/libiconv which is set appropriately
in all environments, so let's use it to fix the issue.
(From OE-Core rev: 255699aeb9275d609e7c03ead69ac902456674dd)
Signed-off-by: André Draszik <adraszik@tycoint.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Having two separate PACKAGECONFIG defaults and settings in two separate
files is confusing. Move all to the common inc file.
(From OE-Core rev: 9e6743e01467ffb08d62b7415fa7af79c09939e0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When compile with readline 5.2:
completer.o: In function `gdb_display_match_list':
completer.c:(.text+0x1c13): undefined reference to `_rl_completion_prefix_display_length'
completer.c:(.text+0x1ce8): undefined reference to `rl_sort_completion_matches'
collect2: ld returned 1 exit status
The --without-system-readline will make it work.
(From OE-Core rev: 94e1b917078bedf73830e54278af77f742c93581)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-ust is too much dependent on glibc dlfcn code
disable it for musl
(From OE-Core rev: eda3a2282b768ce50fa3c719b4f3b692071a498b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #7230]
In certain system configurations TRANSLATED_TARGET_ARCH will not
expand in the right order for gcc-cross-candian-mips64n32 to be
generated properly.
This will cause SDKs to fail to generate properly.
Changing the global definition of TRANSLATED_TARGET_ARCH always
expands the ABIEXTENSION, which causes the OVERRIDES to pick it up
as well. This effectively defines a new class of overrides for the 'n32'.
The side effect is that we need to duplicate some mips64 overrides, and
redefine others that were previously 'n32' or 'mips64' exclusive to have
the correct semantics.
(From OE-Core rev: 4b3a2b703b20583bd107f00a297d972e9bfb514a)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GDB 7.8 added Guile support, and it will auto-detect if Guile is present (which
is non-deterministic, so bad), and if it's present will fail to find the guild
binary as it doesn't consider the sysroot.
For now disable Guile support in GDB, if there is a need to have it enabled in
the future then GDB/Guile can be fixed.
(From OE-Core rev: f7b342a73661cfff4043fab77ab8e9ef0e48dec4)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This solves the following warning:
WARNING: QA Issue: gdb rdepends on zlib, but it isn't a build
dependency? [build-deps]
(From OE-Core rev: 3dc99615b265999206264be33af1258a9c41c7b3)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The class itself currently does nothing. The idea is to mark all recipes that
make use of the texinfo utilities. In the future, this class could be used to
suppress the generation/formatting of documentation for performance,
explicitly track dependencies on these utilities, and eliminate Yocto's
current dependency on the host system's texinfo utilities.
(From OE-Core rev: e6fb2f9afe2ba6b676c46d1eb297ca9cc532d405)
Signed-off-by: Max Eliaser <max.eliaser@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The base_contains is kept as a compatibility method and we ought to
not use it in OE-Core so we can remove it from base metadata in
future.
(From OE-Core rev: d83b16dbf0862be387f84228710cb165c6d2b03b)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix statement indenting and spacing issues that I happened to notice.
(From OE-Core rev: d11e297b007aba625b398c52952ec929c3b02b83)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A lot of our recipes had short one-line DESCRIPTION values and no
SUMMARY value set. In this case it's much better to just set SUMMARY
since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY
is at least useful. I also took the opportunity to fix up a lot of the
new SUMMARY values, making them concisely explain the function of the
recipe / package where possible.
(From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was a floating dependency that got added in recently and was
caught on the Autobuilder, disable building with LZMA to ensure
consistent builds
(From OE-Core rev: 1e58fc8f6ac8f13d6c86a3ae340d90dd53b3ec27)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GDB's configury has a tendency to hard-code the path where it found
libexpat using "-Wl,--rpath". This is undesirable and leads to QA warnings.
Fortunately, the helpful GDB maintainers have provided a "--disable-rpath"
switch to turn this behaviour off. Let's use it and profit.
(From OE-Core rev: 3d70f28cc9612f733b835df139f31c197528677a)
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>
This is a simple upgrade. Dropping the unneeded patches
and adding --disable-werror to configure since thats is
what one of the patch was doing which was dropped.
(From OE-Core rev: 452f26b6d189b9fafba644e41921091925fb6a47)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
