When you have the ports version of pcap installed in addition to the system default pcap configuring yersinia fails and thus the whole install/upgrade. After launching make in /usr/ports/security/yersinia you see this... ===> Extracting for yersinia-0.7 => MD5 Checksum OK for yersinia-0.7.tar.gz. => SHA256 Checksum OK for yersinia-0.7.tar.gz. ===> Patching for yersinia-0.7 ===> Applying FreeBSD patches for yersinia-0.7 ===> yersinia-0.7 depends on package: libnet*>=1.1.2,1 - found ===> Configuring for yersinia-0.7 configure: WARNING: you should use --build, --host, --target checking build system type... i386-portbld-freebsd6.1 checking host system type... i386-portbld-freebsd6.1 checking target system type... i386-portbld-freebsd6.1 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i386-portbld-freebsd6.1-gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of cc... none checking how to run the C preprocessor... cc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for makedepend... /usr/X11R6/bin/makedepend AC_LBL_UNALIGNED_ACCESS: not found checking for main in -lsocket... no checking for main in -lresolv... no checking for main in -lnsl... no checking for main in -lrt... no checking for a complete set of pcap headers... more than one set found in: /usr/local/include /usr/include please wipe out all unused pcap installations ===> Building for yersinia-0.7 make: cannot open Makefile. *** Error code 2 Stop in /usr/ports/security/yersinia. Fix: None known yet. How-To-Repeat: Make sure you have both system default libpcap and the ports version installed and run make in /usr/ports/security/yersinia.
Responsible Changed From-To: freebsd-ports-bugs->se Over to the maintainer.
> When you have the ports version of pcap installed in addition to > the system default pcap configuring yersinia fails and thus the > whole install/upgrade. > > After launching make in /usr/ports/security/yersinia you see this... [...] > checking for a complete set of pcap headers... > > more than one set found in: > /usr/local/include > /usr/include > > please wipe out all unused pcap installations > ===> Building for yersinia-0.7 > make: cannot open Makefile. > *** Error code 2 > > Stop in /usr/ports/security/yersinia. Well, this appears to be a typical case of "works as designed" to me ... The configure script explicitly checks for this situation and in case headers (and thus libraries) are found in multiple locations, emits a warning, that you can't expect the build to succeed. This is not specific behavior of the port, but of the configure file distributed with yersinia for all supported platforms. You could temporarily hide the pcap header and library (either system or port version, but consistently) and then build the port, or just install yersinia from a package. You could also contact the yersinia developers, or develop a patch to configure, that does the right thing (TM). If it is specific to FreeBSD, I could add it to the port, but I'd definitely prefer if you submitted it to the yersinia developers for inclusion in the next release ... Regards, STefan
State Changed From-To: open->closed While the configure script had probably been extended to prevent building on systems with multiple pcap libraries, which can cause hard to diagnose crashes, this problem seems to be a non-issue on FreeBSD. For that reason I have left the check and warning message enabled in configure, but have disabled the exit command (and thus converted the fatal error to a mere warning ...) This should not cause any problems under FreeBSD, and without this hack, the port would not build on FreeBSD-4.x systems. Thanks for bringing this issue up!