Building imapproxy-1.0_1.txz (origin /buildshare/ports/355755/net/imapproxy) for powerpc-10-0 on XXX Pre-existing file system for this slot! slot2: removed slot2: created x distfiles/ x distfiles/imapproxy-1.0.tar.gz x packages/ x packages/pkg-1.2.7_2.txz ELF ldconfig path: /lib /usr/lib /usr/lib/compat Make depends ===> imapproxy-1.0_1 depends on file: /usr/local/sbin/pkg - not found ===> Verifying install for /usr/local/sbin/pkg in /buildshare/ports/355755/ports-mgmt/pkg ===> Installing existing package /packages/pkg-1.2.7_2.txz Installing pkg-1.2.7_2... done If you are upgrading from the old package format, first run: # pkg2ng ===> Returning to build of imapproxy-1.0_1 Make install ===> imapproxy-1.0_1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by imapproxy-1.0_1 for building ===> Extracting for imapproxy-1.0_1 => SHA256 Checksum OK for imapproxy-1.0.tar.gz. ===> Patching for imapproxy-1.0_1 ===> Applying FreeBSD patches for imapproxy-1.0_1 ===> Configuring for imapproxy-1.0_1 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/net/imapproxy/work/imapproxy-1.0/configure creating cache ./config.cache checking host system type... powerpc-unknown-freebsd11.0 checking target system type... powerpc-unknown-freebsd11.0 checking build system type... powerpc-unknown-freebsd11.0 checking for gcc... cc checking whether the C compiler (cc -O2 -pipe -fno-strict-aliasing ) works... yes checking whether the C compiler (cc -O2 -pipe -fno-strict-aliasing ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether cc accepts -g... yes checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel checking how to run the C preprocessor... cpp checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for fcntl.h... yes checking for strings.h... yes checking for sys/ioctl.h... yes checking for sys/time.h... yes checking for syslog.h... yes checking for unistd.h... yes checking for working const... yes checking for pid_t... yes checking whether time.h and sys/time.h may both be included... yes checking return type of signal handlers... void checking for select... yes checking for socket... yes checking for strdup... yes checking for strerror... yes checking for strstr... yes checking for strtol... yes updating cache ./config.cache creating ./config.status creating Makefile ===> Building for imapproxy-1.0_1 cc -O2 -pipe -fno-strict-aliasing -I./include -c network.c In file included from network.c:34: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c output.c In file included from output.c:30: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c database.c In file included from database.c:33: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c splitstring.c In file included from splitstring.c:26: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c configfile.c In file included from configfile.c:34: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c base64.c cc -O2 -pipe -fno-strict-aliasing -I./include -c misc.c In file included from misc.c:34: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c processing_parent.c In file included from processing_parent.c:44: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c processing_child.c In file included from processing_child.c:43: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c parsed_message.c In file included from parsed_message.c:27: ./include/output.h:29: warning: conflicting types for built-in function 'log' cc -O2 -pipe -fno-strict-aliasing -I./include -c imapproxy.c In file included from imapproxy.c:29: ./include/output.h:29: warning: conflicting types for built-in function 'log' imapproxy.c: In function 'main': imapproxy.c:65: warning: incompatible implicit declaration of built-in function 'exit' cc -O2 -pipe -fno-strict-aliasing -I./include network.o output.o database.o splitstring.o configfile.o base64.o misc.o processing_parent.o processing_child.o parsed_message.o imapproxy.o -o imapproxy ===> Staging for imapproxy-1.0_1 ===> Generating temporary packing list install -s -o root -g wheel -m 555 /obj/buildshare/ports/355755/net/imapproxy/work/imapproxy-1.0/imapproxy /obj/buildshare/ports/355755/net/imapproxy/work/stage/usr/local/sbin install -o root -g wheel -m 444 /obj/buildshare/ports/355755/net/imapproxy/work/imapproxy-1.0/example.conf /obj/buildshare/ports/355755/net/imapproxy/work/stage/usr/local/etc/imapproxy.conf.dist ====> Compressing man pages (compress-man) ===> Installing for imapproxy-1.0_1 ===> Checking if net/imapproxy already installed ===> Registering installation for imapproxy-1.0_1 Installing imapproxy-1.0_1... done ===> SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/sbin/imapproxy If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.kuleuven.net/projects/imapproxy/ Make package ===> Building package for imapproxy-1.0_1 slot2: removed