Your message dated Sun, 6 Jan 2019 12:07:22 +0200
with message-id
<CAD=WrcJ3F6G1f=4eqcoe4xgz4enxjwknrocoqcpzvxgukrq...@mail.gmail.com>
and subject line Re: plastimatch FTBFS with libdlib-dev 19.10-1
has caused the Debian Bug report #895741,
regarding plastimatch FTBFS with libdlib-dev 19.10-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895741
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libdlib-dev
Version: 19.10-2
Severity: serious
Control: affects -1 src:plastimatch
https://buildd.debian.org/status/package.php?p=plastimatch&suite=sid
...
-- Configuring done
CMake Warning (dev) at cmake/PlmMacros.cmake:66 (add_library):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target. Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.
Target "plmbase" links to target "dlib::dlib" but the target was not found.
Perhaps a find_package() call is missing for an IMPORTED target, or an
ALIAS target is missing?
Call Stack (most recent call first):
src/plastimatch/base/CMakeLists.txt:241 (plm_add_library)
...
/usr/bin/c++ -fPIC -g -O2
-fdebug-prefix-map=/<<BUILDDIR>>/plastimatch-1.7.0+dfsg.1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,now -Wl,--as-needed
-shared -Wl,-soname,libplmsys.so.1.7 -o ../../../libplmsys.so.1.7
CMakeFiles/plmsys.dir/delayload.c.o CMakeFiles/plmsys.dir/dir_list.cxx.o
CMakeFiles/plmsys.dir/dlib_threads.cxx.o CMakeFiles/plmsys.dir/file_util.cxx.o
CMakeFiles/plmsys.dir/logfile.cxx.o CMakeFiles/plmsys.dir/option_range.cxx.o
CMakeFiles/plmsys.dir/path_util.cxx.o CMakeFiles/plmsys.dir/plm_endian.cxx.o
CMakeFiles/plmsys.dir/plm_fwrite.cxx.o CMakeFiles/plmsys.dir/plm_sleep.cxx.o
CMakeFiles/plmsys.dir/plm_timer.cxx.o
CMakeFiles/plmsys.dir/print_and_exit.cxx.o
CMakeFiles/plmsys.dir/string_util.cxx.o
-L/<<BUILDDIR>>/plastimatch-1.7.0+dfsg.1/obj-x86_64-linux-gnu/libs/liblbfgs-1.9
-L/<<BUILDDIR>>/plastimatch-1.7.0+dfsg.1/obj-x86_64-linux-gnu/libs/specfun
-L/<<BUILDDIR>>/plastimatch-1.7.0+dfsg.1/obj-x86_64-linux-gnu -L/usr/include
-ldlib::dlib -ldl -lpthread
/usr/bin/x86_64-linux-gnu-ld: cannot find -ldlib::dlib
collect2: error: ld returned 1 exit status
make[3]: *** [src/plastimatch/sys/CMakeFiles/plmsys.dir/build.make:411:
libplmsys.so.1.7] Error 1
Not sure whether this is the correct fix, but plastimatch builds
after editing /usr/lib/x86_64-linux-gnu/cmake/dlib/dlibConfig.cmake
to remove the if/endif block around
get_filename_component(dlib_CMAKE_DIR "${CMAKE_CURRENT_LIST_FILE}" PATH)
include("${dlib_CMAKE_DIR}/dlib.cmake")
--- End Message ---
--- Begin Message ---
On Tue, 15 May 2018 23:50:49 -0400 Hugo Lefeuvre <[email protected]> wrote:
> Hi Adrian,
>
> Yes, it is most likely a bug in the dlib package. Last dlib updates made
> Debian packaging considerably trickier by separating build of static
> files and build of shared libraries. I have just noticed that we ship
> the cmake config files of the shared build into the -dev package, which
> might be the source of your problems. In fact, we should rather ship the
> files produced by the static build (but still, I'm not 100% it's going to
> be sufficient).
>
> I have just prepared an upload addressing this issue, but I had
> difficulties to build plastimatch with dlib 19.1 (configuration issues,
> plastimatch seems to to use deprecated directives), so I couldn't really
> test it.
>
> You can find test packages here[0]. Can you try them ?
Dear Hugo,
I can confirm that plastimatch does build with dlib 19.10, so this issue is
resolved; thanks!
--- End Message ---
