Bug#1011677: ignition-common: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libfreeimage.so.3: undefined reference to `_TIFFDataSize at LIBTIFF_4.0'

[Lucas Nussbaum]

Source: ignition-common
Version: 4.5.0+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now CMakeFiles/UNIT_GTSMeshUtils_TEST.dir/GTSMeshUtils_TEST.cc.o -o ../../bin/UNIT_GTSMeshUtils_TEST  -Wl,-rpath,/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/lib ../../lib/libgtest.a ../../lib/libgtest_main.a ../../lib/libignition-common4-graphics.so.4.5.0 -lpthread ../../lib/libgtest.a ../../lib/libignition-common4.so.4.5.0 -lpthread /usr/lib/x86_64-linux-gnu/libuuid.so /usr/lib/x86_64-linux-gnu/libuuid.so /usr/lib/x86_64-linux-gnu/libignition-math6.so.6.10.0 
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfreeimage.so.3: undefined reference to `_TIFFDataSize at LIBTIFF_4.0'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ignition-common_4.5.0+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&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 marking 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.