rpm vs --compress-debug-sections=zlib

[Vít Ondruch]

Hi,

Recently, there have started to appear weird messages in the build
output of development snapshot of Ruby [1]:


```

... snip ...

+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz
--dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000
/builddir/build/BUILD/ruby-2.4.0-r56693

... snip ...

extracting debug info from
/builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56693.fc26.x86_64/usr/lib64/libruby.so.2.4.0
/usr/lib/rpm/debugedit:
/builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56693.fc26.x86_64/usr/lib64/libruby.so.2.4.0:
DWARF version 0 unhandled
extracting debug info from
/builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56693.fc26.x86_64/usr/bin/ruby-mri

... snip ...

dwz: ./usr/lib64/libruby.so.2.4.0.debug: DWARF version 0 unhandled

... snip ...

```


This was apparently introduced by upstream commit [2], which adds
"--compress-debug-sections=zlib" as one of linker options. What I
actually don't understand what are the implications of this.

* It seems that RPM cannot handle the compressed debug info properly,
does it also mean that the debuginfo is not stripped?

* Should I ask RPM guys to add support for this?

* Should I remove this flag? Should I ask upstream to make the
compression optional?


Vít



[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=16383886

[2]
https://github.com/ruby/ruby/commit/a40d95c48fa7e7974feb294abca8af34e299d109