From owner-freebsd-ports@FreeBSD.ORG Tue Jul 22 23:56:17 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2FB6106566C for ; Tue, 22 Jul 2008 23:56:17 +0000 (UTC) (envelope-from mldodson@comcast.net) Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id AED618FC08 for ; Tue, 22 Jul 2008 23:56:17 +0000 (UTC) (envelope-from mldodson@comcast.net) Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA09.westchester.pa.mail.comcast.net with comcast id tAqC1Z00317dt5G59BgGBu; Tue, 22 Jul 2008 23:40:16 +0000 Received: from wotan.mlandml.net ([98.198.9.238]) by OMTA13.westchester.pa.mail.comcast.net with comcast id tBfq1Z00K588yLJ3ZBfrJd; Tue, 22 Jul 2008 23:39:51 +0000 X-Authority-Analysis: v=1.0 c=1 a=osZgN4nW1hEA:10 a=goZ887lJWtQA:10 a=rITDv7nW5hcA:10 a=cOYuRaPrs3txQUr7vgIA:9 a=donC4Rgwcts3x4mS1aQA:9 a=tUxVEHyADy2ngMVD6HV93RfoNxwA:4 a=gi0PWCVxevcA:10 Message-ID: <48866FDF.9030903@comcast.net> Date: Tue, 22 Jul 2008 18:40:15 -0500 From: "M. L. Dodson" User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Help for a problematic port to replace biology/nab X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@comcast.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2008 23:56:18 -0000 I am the maintainer of biology/nab and asked that it be marked deprecated several months ago. I just filed a PR to have it removed. Nab has been superseded by AmberTools (also by the nab developers). I have the current version of AmberTools building with no problems from within a skeleton port. The problem (and I do not see any solution) is that AmberTools assumes that it will be built in its final installed location. This location is hardwired throughout the compiled code. The build process fails spectacularly if you specify some other location, then move the built code and data. Is there some secret method to handle such ports for which I do not possess the magical decoder ring? Any help would be appreciated. Bud Dodson -- M. L. Dodson Email: mldodson-at-comcast-net Phone: eight_three_two-five_63-386_one