On 29.09.19 11:08, Niels Thykier wrote:
Control: tags -1 moreinfo
On Tue, 24 Sep 2019 09:07:16 +0200 Matthias Klose <[email protected]> wrote:
Package: debhelper
Version: 12.6.1
For packages needing debug information for backtraces or stack unwinding in the
binary itself, it's not possible to pass custom strip optons to strip, having to
mimic the dh_strip behavior in the rules when you require different options for
stripping. Also with the proposed new CTF debug format package might want to
keep the relatively small CTF overhead instead of the rather large DWARF debug
information.
There is also discussion at [1] how upstream strip should handle stripping CTF.
[1] https://sourceware.org/ml/binutils/2019-09/msg00209.html
I am getting mixed signals from this bug report. AFAICT, upstream wants
CTF never to be stripped. While we can argue whether that is what we
want, I don't see how it is related to passing custom options to strip.
well, then let's separate the ctf issue and the passing of custom options (and I
found again #595810).
Notably, dh_strip should DTRT by default and not require that every
packager knows every little detail about the ELF format and various ELF
sections.
I agree with that, however upstream doesn't want to have any new options to do
something what the distro wants to do. So from my point of view it's the distro
tools which should abstract on the section names.
What I currently see is that dh_strip implements the default option and doesn't
offer any help for the non-default.
As for passing custom options:
* How many cases do you have where you need to pass custom options and
it is the *same* custom options for every ELF binary/static lib in
that debian package?
How would you build an openjdk-11 dbgsym package with custom options applied, so
that the jmap tool is still working? The current source builds a manual dbg
package and already has to re-implement the dh_strip logic. If you need to
replicate the logic to build a dbgsym package, then that's even more duplication.
What am I missing for that use case?
