Date: Tue, 24 Dec 2019 03:11:26 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 242842] security/suricata fails to compile (5.0.0 PV=2) Message-ID: <bug-242842-7788-jsbYFHun0s@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242842-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-242842-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242842 --- Comment #2 from A Sharp <asharp@iqonline.net> --- Spun up a VM with 12.1-RELEASE and *only* compiled Suricata (via ports, with dependencies). Installed just fine. One thing notably different is that on the VM, there's are no /^py36-/ modules installed. On the device where the error occurred - there is a good sized list of /^py36-/ modules installed. The primary items needed on this device: - Apache24 - Squid - Samba (required by Squid for Auth) - Suricata - Snort Is there a way to determine which/what port(s) are fixating on Python 3.6?= =20 Recall that something required llvm80, which required python36 - however, cannot recall what started the requirement for all the py36 modules. Doing= a "make all-depends-list" for Suricata revealed that it wanted python v2.7 and v3.7 (seems odd, no?) I'd need to go back and try each of the installed po= rts to try to figure out what/why the py36 modules were injected? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242842-7788-jsbYFHun0s>