Can't compile talpa for kernel 4.13 in Debian

Question

Hello 
 uname -r 4.13.0-1-amd64 
 gcc --version gcc (Debian 7.2.0-11) 7.2.0 
 
 /talpa_select select [Talpa-select] Copyright 1989-2017 Sophos Limited. All rights reserved. Mon Oct 23 15:41:44 2017 GMT Linux distribution: [debian] Product: [Debian GNU/Linux 8.9 (jessie)] Kernel: [4.13.0-1-amd64] Multiprocessor support enabled. Searching for source pack... Searching for suitable binary pack... No suitable binary pack available. Preparing for build... Extracting sources... Configuring build of version 1.23.3... Building... Error: Failed to build from source.

Here are the last messages in log 
 configure: creating ./config.status config.status: creating makefile config.status: creating clients/Makefile config.status: creating tests/Makefile config.status: creating tests/modules/makefile config.status: creating tests/benchmark/Makefile config.status: creating config.h config.status: executing depfiles commands 
 Building... Traceback (most recent call last): File "talpa_select.py", line 2216, in _action File "talpa_select.py", line 845, in select File "talpa_select.py", line 1736, in select File "talpa_select.py", line 1820, in build File "talpa_select.py", line 1973, in __try_build SelectException: exc-build-failed

What happened? 
 
 As the option seems ok 
 
 root@debian:/boot# grep -i fanotify config-4.13.0-1-amd64 CONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y

I used
 savconfig set PreferFanotify true 
 
 After reboot, it looks ok 
 root@debian:/boot# journalctl | grep savd oct. 23 18:25:23 debian kernel: savd (1308): Using fanotify permission checks may lead to deadlock; tainting kernel oct. 23 18:25:23 debian savd[781]: savd.daemon: SAVD-STARTED oct. 23 18:25:43 debian savd[781]: savd.daemon: ONACCESS-ENABLED fanotify root@debian:/boot#

DouglasLeeder · Accepted Answer

The github perforce branch has a fix on it now. 
 You can use autodeploy.sh to try that out on your machine. - gist.github.com/.../7892031

grand toubab · Answer

Hello 
 I uses the script autodeploy in my install directory /opt/av-sophos 
 root@debian:/opt/av-sophos# ls autodeploy.sh doc etc lib log resul-autodeploy.txt share talpa2 uncdownload update bin engine include lib64 mcs rms talpa tmp uninstall.sh var 
 root@debian:/opt/av-sophos# bash autodeploy.sh /opt/av-sophos/talpa2 
 then manually copy 
 root@debian:/opt/av-sophos/talpa2# cp -v talpa-srcpack.tar.gz /opt/av-sophos/talpa/override 
 and then it looks ok 
 root@debian:/opt/av-sophos/engine# ./talpa_select select [Talpa-select] Copyright 1989-2017 Sophos Limited. All rights reserved. Mon Oct 30 16:53:06 2017 GMT Linux distribution: [debian] Product: [Debian GNU/Linux 8.9 (jessie)] Kernel: [4.13.0-1-amd64] Multiprocessor support enabled. Searching for source pack... Searching for suitable binary pack... No suitable binary pack available. Preparing for build... Extracting sources... Configuring build of version 0.9.95... Building... Installing binaries... Creating local binary pack... root@debian:/opt/av-sophos/engine# 
 root@debian:/opt/av-sophos/bin# ./savconfig set PreferFanotify false 
 root@debian:/opt/av-sophos/bin# systemctl restart sav-protect.service 
 root@debian:/opt/av-sophos/bin# systemctl status sav-protect.service ● sav-protect.service - "Sophos Anti-Virus daemon" Loaded: loaded (/lib/systemd/system/sav-protect.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-10-30 18:11:39 CET; 2min 7s ago Docs: man:sav-protect Process: 15209 ExecStop=/opt/av-sophos/engine/.sav-protect.systemd.stop.sh (code=exited, status=0/SUCCESS) Process: 15266 ExecStartPost=/opt/av-sophos/engine/.sav-protect.systemd.poststart.sh (code=exited, status=0/SUCCESS) Process: 15233 ExecStartPre=/opt/av-sophos/engine/.sav-protect.systemd.prestart.sh (code=exited, status=0/SUCCESS) Main PID: 15265 (savd) Tasks: 34 (limit: 4915) CGroup: /system.slice/sav-protect.service ├─15265 savd etc/savd.cfg ├─15327 savscand --incident=unix://tmp/incident --namedscan=unix://root@tmp/namedscansprocessor.0 --ondemandcont └─15371 savscand --incident=unix://tmp/incident socketpair://45/46 --threads=5 
 
 root@debian:/opt/av-sophos/bin# journalctl | grep savd 
 oct. 30 17:53:53 debian savd[680]: talpa_select.compiled: TALPA-COMPILED oct. 30 18:11:19 debian savd[680]: savd.daemon: ONACCESS-DISABLED oct. 30 18:11:19 debian savd[680]: savd.daemon: SAVD-STOPPED oct. 30 18:11:24 debian savd[15265]: savd.daemon: SAVD-STARTED oct. 30 18:11:36 debian savd[15265]: savd.daemon: ONACCESS-ENABLED talpa 
 
 By the way the talpa_select displays wrong information about Debian, better if you use the PRETTY_NAME 
 cat /etc/os-release 
 PRETTY_NAME="Debian GNU/Linux buster/sid" NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@debian:/#