[Pkg-deepin-devel] Bug#951992: deepin-screen-recorder: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209'

[Lucas Nussbaum]

Source: deepin-screen-recorder
Version: 5.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> g++ -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu -o deepin-screen-recorder main.o main_window.o record_process.o settings.o utils.o record_button.o record_option_panel.o countdown_tooltip.o constant.o event_monitor.o start_tooltip.o button_feedback.o process_tree.o qrc_deepin-screen-recorder.o moc_main_window.o moc_record_process.o moc_settings.o moc_record_button.o moc_record_option_panel.o moc_countdown_tooltip.o moc_event_monitor.o moc_start_tooltip.o moc_button_feedback.o moc_process_tree.o   -lX11 -lXext -lXtst -Llibprocps -lprocps -lxcb-util -lxcb -ldtkwidget -ldtkwm -ldtkcore /usr/lib/x86_64-linux-gnu/libQt5Widgets.so /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so /usr/lib/x86_64-linux-gnu/libQt5Gui.so /usr/lib/x86_64-linux-gnu/libQt5Network.so /usr/lib/x86_64-linux-gnu/libQt5DBus.so /usr/lib/x86_64-linux-gnu/libQt5Core.so /usr/lib/x86_64-linux-gnu/libGL.so -lpthread   
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209'
> /usr/bin/ld: /lib/x86_64-linux-gnu/libsystemd.so.0: error adding symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/deepin-screen-recorder_5.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.