I briefly looked into this.
The offending binares are /usr/bin/pipewire and /usr/bin/pipewire-pulse
On amd64 I get:
# objdump -g pipewire-pulse | tail -n 5
Contents of the .gnu_debuglink section (loaded from pipewire-pulse):
Separate debug info file: aecb16cbc8f77084957492db3828061b543732.debug
CRC value: 0xc80d0d48
# objdump -g pipewire | tail -n 5
Contents of the .gnu_debuglink section (loaded from pipewire):
Separate debug info file: aecb16cbc8f77084957492db3828061b543732.debug
CRC value: 0xe4077046
Looking at src/daemon/meson.build I see
pipewire_exec = executable('pipewire',
pipewire_daemon_sources,
install: true,
c_args : pipewire_c_args,
include_directories : [configinc, spa_inc],
dependencies : [pipewire_dep, ],
)
executable('pipewire-pulse',
pipewire_daemon_sources,
install: true,
c_args : pipewire_c_args,
include_directories : [configinc, spa_inc],
dependencies : [pipewire_dep, ],
)
Basically, we build the same binary twice, the only difference is the
executable name.
I guess we could just as well ship a symlink /usr/bin/pipewire-pulse → /usr/bin/pipewire ? Dylan, do you know why upstream basically builds the same executable twice?The binary behaves differently when called with a different name, but a symlink would just as well do in this case.
Regards, Michael
OpenPGP_signature
Description: OpenPGP digital signature
