From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Sep 15 10:20:04 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D10941065670 for ; Thu, 15 Sep 2011 10:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A6A568FC14 for ; Thu, 15 Sep 2011 10:20:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8FAK4YS051236 for ; Thu, 15 Sep 2011 10:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8FAK4TS051235; Thu, 15 Sep 2011 10:20:04 GMT (envelope-from gnats) Date: Thu, 15 Sep 2011 10:20:04 GMT Message-Id: <201109151020.p8FAK4TS051235@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Michael Scheidell Cc: Subject: Re: ports/160742: mail/p5-Mail-SpamAssassin Install error X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michael Scheidell List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 10:20:04 -0000 The following reply was made to PR ports/160742; it has been noted by GNATS. From: Michael Scheidell To: , Cc: Subject: Re: ports/160742: mail/p5-Mail-SpamAssassin Install error Date: Thu, 15 Sep 2011 06:12:00 -0400 Thanks. on complex problems, its best to totally document it so that if we find a solution, others can search for help also. There is nothing specifically in any of the ports files for p5-Mail-SpamAssassin that would break if you use Freebsd7.0, so I doubt the problem is there. Also, since no one else has reported a problem, lets assume that it is something unique to your installation, or version. First: make sure you have a totally clean ports, updated ports tree. (SA port is up to 3.3.2_2 as of 2 weeks ago, so I know you are out of data) if you use cvsup, then cd /usr/ports and do a make update if you use portsnap, do a portsnap fetch update do a portsclean of old work files., portsclean -C or if you don't have that installed, rm -rf /usr/ports/*/*/work Check the version of perl you are using. only perl version 5.8.8 or above is supported by SA itself. if you upgraded perl, then review /usr/ports/UPDATING to make sure you didn't take any shortcuts. Upgrading perl is broken, always has been, always will be. run perl-after-upgrade -f if none of this helps, you might try a 'greenfields' install of 7.0 (test computer or vm image, install clean 7.0 and try to install SA). If a clean install works, then you have a corrupted posts install somewhere. if a clean install still fails, than is most likely a change in ports structure somewhere from freebsd 7.0 to 7.4 Now: since you are running an unsupported version of freebsd, you may still have problems with the ports tree structure, and .mk include files. You may also have problems with any dependent files, libraries or perl modules. You only option is to upgrade to a supported version of freebsd. Sorry I could not help further, you might be able to find more here, specifically, information about finding a older ports tree tagged Good luck, and thanks for supporting Freebsd. ______________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ ______________________________________________________________________