Open wdoekes opened 1 day ago
https://lists.debian.org/debian-devel/2016/05/msg00199.html
The option is 'nostrip'. It also seems redundant now, given that the default is to distribute debug symbols separately rather than to strip them entirely.
Finally found this: https://manpages.ubuntu.com/manpages/focal/man1/dh_strip.1.html
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1 "Binaries"). This will also inhibit the automatic creation of debug symbol packages.
SONIC_DEBUGGING_ON=y
setsDEB_BUILD_OPTIONS=nostrip
and for certain packages, this causes dbgsym packages to not be produced.Upstream bug: #-5982.
Getting no dbgsym package when debugging is on feels like the inverse of what we expect.
See this:
Set
SONIC_DEBUGGING_ON=y
inrules/config
^- failure
Unset
SONIC_DEBUGGING_ON=y
inrules/config
^- success
Example with nostrip:
^- no
ipmitool-dbgsym_1.8.19-4+deb12u1_amd64.deb
created^- now both files are created
I did find this on the internet: https://lists.debian.org/debian-devel/2015/05/msg00472.html
But not so much info here: https://manpages.debian.org/testing/debhelper/debhelper-compat-upgrade-checklist.7.en.html
I'm not entirely sure why/what. It could be the debhelper/compat mode that is related, or there is something else that I haven't seen yet. But the results speak for themselves: nostrip is not an expected feature, because the it breaks the build which expects the ipmitool-dbgsym to be built.
Perhaps we want
DEB_BUILD_OPTIONS_GENERIC := debug
instead?