[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1064711: libplacebo: FTBFS: ld: cannot find -lexecinfo: No such file or directory



Source: libplacebo
Version: 6.338.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld -plugin /usr/libexec/gcc/x86_64-linux-gnu/13/liblto_plugin.so -plugin-opt=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper -plugin-opt=-fresolution=/tmp/ccg4YCWX.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker /lib64/ld-linux-x86-64.so.2 -pie /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/Scrt1.o /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/13 -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/13/../../.. --version -z relro -z now -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/x86_64-linux-gnu/13/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crtn.o
> -----------
> Sanity testing C++ compiler: c++
> Is cross compiler: False.
> Sanity check compiler command line: c++ sanitycheckcpp.cc -o sanitycheckcpp.exe -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now
> Sanity check compile stdout:
> 
> -----
> Sanity check compile stderr:
> 
> -----
> Running test binary command:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/sanitycheckcpp.exe
> C++ compiler for the build machine: c++ (gcc 13.2.0 "c++ (Debian 13.2.0-13) 13.2.0")
> C++ linker for the build machine: c++ ld.bfd 2.42
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Target machine cpu family: x86_64
> Target machine cpu: x86_64
> Running compile:
> Working directory:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpp3_6noyk
> Code:
>  extern int i;
> int i;
> 
> -----------
> Command line: `cc /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpp3_6noyk/testfile.c -o /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpp3_6noyk/output.obj -c -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -O0 -Wincompatible-pointer-types` -> 0
> Compiler for C supports arguments -Wincompatible-pointer-types: YES 
> Running compile:
> Working directory:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp74qc2g_a
> Code:
>  int main(void) { return 0; }
> 
> -----------
> Command line: `cc /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp74qc2g_a/testfile.c -o /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp74qc2g_a/output.exe -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -O0 -Wl,--fatal-warnings -Wl,--exclude-libs=ALL -Wl,-z,relro -Wl,-z,now` -> 0
> Compiler for C supports link arguments -Wl,--exclude-libs=ALL: YES 
> Running compile:
> Working directory:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp1dvdaolk
> Code:
>  int main(void) { return 0; }
> 
> -----------
> Command line: `cc /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp1dvdaolk/testfile.c -o /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmp1dvdaolk/output.exe -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lm -Wl,--end-group -Wl,--allow-shlib-undefined -Wl,-z,relro -Wl,-z,now` -> 0
> Library m found: YES
> Program python3 found: YES (/usr/bin/python3)
> Run-time dependency threads found: YES
> Running compile:
> Working directory:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpjm1qw8yl
> Code:
>  
>         #include <pthread.h>
>         int main(void) {
>             /* If it's not defined as a macro, try to use as a symbol */
>             #ifndef pthread_condattr_setclock
>                 pthread_condattr_setclock;
>             #endif
>             return 0;
>         }
> -----------
> Command line: `cc /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpjm1qw8yl/testfile.c -o /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpjm1qw8yl/output.obj -c -pthread -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -O0 -std=c11 -D_ISOC99_SOURCE -D_ISOC11_SOURCE -D_GNU_SOURCE -U__STRICT_ANSI__ -Wmissing-prototypes -Wno-sign-compare -Wno-unused-parameter -Wno-missing-field-initializers -Wno-type-limits -Werror=implicit-function-declaration -Werror=incompatible-pointer-types` -> 0
> Header "pthread.h" has symbol "pthread_condattr_setclock" with dependency threads: YES 
> Pkg-config binary missing from cross or native file, or env var undefined.
> Trying a default Pkg-config fallback at pkg-config
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Determining dependency 'libunwind' with pkg-config executable '/usr/bin/pkg-config'
> env[PKG_CONFIG_PATH]: 
> env[PKG_CONFIG]: /usr/bin/pkg-config
> -----------
> Called: `/usr/bin/pkg-config --modversion libunwind` -> 1
> stderr:
> Package libunwind was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libunwind.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libunwind', required by 'virtual:world', not found
> -----------
> CMake binary for host machine is not cached
> CMake binary missing from cross or native file, or env var undefined.
> Trying a default CMake fallback at cmake
> Did not find CMake 'cmake'
> Found CMake: NO
> CMake binary for machine host machine not found. Giving up.
> Run-time dependency libunwind found: NO (tried pkgconfig and cmake)
> Running compile:
> Working directory:  /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpqy3jm0tm
> Code:
>  int main(void) { return 0; }
> 
> -----------
> Command line: `cc /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpqy3jm0tm/testfile.c -o /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-private/tmpqy3jm0tm/output.exe -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lexecinfo -Wl,--end-group -Wl,--allow-shlib-undefined -Wl,-z,relro -Wl,-z,now` -> 1
> stderr:
> /usr/bin/ld: cannot find -lexecinfo: No such file or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/libplacebo_6.338.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240224&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.


Reply to: