From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist <ptxdist@pengutronix.de>
Subject: [ptxdist] Should GDB select XZ?
Date: Tue, 7 May 2024 14:39:01 +0100 [thread overview]
Message-ID: <3ec54e2f-eb27-4b3d-a73f-4bb3d937a136@mev.co.uk> (raw)
Hi,
The configure script of GDB (version 7.6 or later) has a --with-lzma
option that controls whether GDB will use liblzma or not. (It is needed
to for reading .gnu_debuginfo sections from ELF files, if they are
present.) By default (if not explicitly enabled or disabled), it will
use liblzma if it is detected at build time.
Currently, PTXdist does not configure GDB with any --with-lzma value, so
whether or not it is configured to use liblzma depends on whether some
version of XZ has previously been built or not.
If GDB gets automatically configured to use liblzma, but the XZ package
is not to be installed (perhaps there is a previous build of XZ in the
platform's sysroot-target), then there will be a run-time error when
running GDB due to the missing library. It also means that the build of
GDB may not be reproducible.
It seems to me that PTXdist should have a configuration option to choose
whether GDB should be built with liblzma support or not (and possibly a
configuration option to select whether the GDB version is 7.6 or later,
defaulting to true). The default could depend on
PTXCONF_TARGET_MINI_DEBUGINFO. If binaries have a .gnu_debuginfo
section then we probably want GDB to be able to use it!
I'll attempt to knock up a patch for it.
--
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=-
-=( registered in England & Wales. Regd. number: 02862268. )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
next reply other threads:[~2024-05-07 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 13:39 Ian Abbott [this message]
2024-05-09 10:15 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ec54e2f-eb27-4b3d-a73f-4bb3d937a136@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox