Autospec and Stripping binaries

Kingfisher · July 17, 2024, 6:41am

Is compilation of full-debug-info required for no-strip? What is the purpose?

clearlinux/autospec/blob/b858a2a99030e8b8ee8794829f7c00387af216f5/autospec/specfiles.py#L212-L218


      
          
          def write_strip_command(self):
              """Write commands to prevent stripping binary if requested."""
              if self.config.config_opts['nostrip'] or not self.config.config_opts['full-debug-info']:
                  self._write("# Suppress stripping binaries\n")
                  self._write("%define __strip /bin/true\n%define debug_package %{nil}\n")

arjan · July 17, 2024, 3:34pm

so we have two models:

include most debug info in the binary that is shipped in the OS image (default)
have separate debug info that we magically download on demand if you run a debugger (used to be default, but we’re switching to #1 by default)

full-debug-info is #2 ,… and we mostly use it for cases where the built in debug info is disproportionally large

you can also prevent stripping altogether, mostly for cases where “strip” would break a binary
… which is the nostrip option

Topic		Replies	Views
Clearing /var/cache/ Developer Discussion	0	615	June 8, 2022
Derivative Distribution Documentation	12	1360	November 14, 2019
Unclear documentation around Telemetry Documentation	7	1715	February 3, 2022
Clearing up Autospec mock folder General Discussion	0	264	June 1, 2022
USe ClearLinux as Rust and Python developper? General Discussion	0	368	October 21, 2021

Autospec and Stripping binaries

Related topics