>is due to Debian specific changes to the pcap-config tool. This
>starting space in the output might also break other projects using
>libpcap and cmake.
>
>What do you think? If you want I can take care of filing that bug.
yes please, I think this is worth a bug
G.
Hi,
while I'm not against introducing the patch, in my opinion we should
file a bug against libpcap0.8-dev instead (or at least in addition).
The starting space in the output of
pcap-config --libs
is due to Debian specific changes to the pcap-config tool. This
starting space in the output
Control: tag -1 + patch
Hello,
On Mon, 18 Sep 2017, SZ Lin wrote:
> CMake Error at nasl/CMakeLists.txt:147 (add_library):
> Target "openvas_nasl_shared" links to item " -lpcap" which has leading or
> trailing whitespace. This is now an error according to policy CMP0004.
>
> This issue is caused
I have took some time to investigate this issue
--
CMake Error at misc/CMakeLists.txt:125 (add_library):
Target "openvas_misc_shared" links to item " -lpcap" which has leading or
trailing whitespace. This is now an error according to policy CMP0004.
CMake Error at nasl/CMakeLists.txt:147
Source: openvas-libraries
Version: 9.0.1-3
Severity: serious
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/openvas-libraries_9.0.1-3.rbuild.log
...
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
5 matches
Mail list logo
