From owner-freebsd-ports@FreeBSD.ORG Tue Mar 13 14:13:52 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 55FE1106564A for ; Tue, 13 Mar 2012 14:13:52 +0000 (UTC) (envelope-from admin@vizion2000.net) Received: from dns1.vizion2000.net (dns1.vizion2000.net [62.49.197.50]) by mx1.freebsd.org (Postfix) with ESMTP id DA52B8FC14 for ; Tue, 13 Mar 2012 14:13:51 +0000 (UTC) Received: by dns1.vizion2000.net (Postfix, from userid 1004) id BE970119C26; Tue, 13 Mar 2012 06:01:52 -0700 (PDT) From: David Southwell Organization: Vizion Communications To: ports@freebsd.org Date: Tue, 13 Mar 2012 06:01:52 -0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-RELEASE; KDE/4.7.3; amd64; ; ) X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201203130601.52466.admin@vizion2000.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: qpopper compile failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: david@vizion2000.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 14:13:52 -0000 qpopper has been working fine (amd64 running postfix) but on portupgrade I am Getting the following error: set MISSING_OBJS to base64.o set MISSING_SRCS to base64.c Set AR_FLAG = -r ; RANLIB_CMD = checking for sendmail program... ERROR: The sendmail program cannot be located ===> Script "configure" failed unexpectedly. sendmail is [root@dns1 /usr/ports/mail/qpopper]# whereis sendmail sendmail: /usr/local/sbin/sendmail /usr/local/man/man1/sendmail.1.gz /usr/src/usr.sbin/sendmail qpopper config log includes the following lines: PATH: /usr/local/kde4/bin PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/share/lprof PATH: /usr/local/bin PATH: /home/admin/bin Does anyone have any idea why this error might occur?