From owner-freebsd-ports@FreeBSD.ORG Wed Jul 23 02:08:40 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 AE41C1065674 for ; Wed, 23 Jul 2008 02:08:40 +0000 (UTC) (envelope-from mldodson@comcast.net) Received: from QMTA07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id A292C8FC14 for ; Wed, 23 Jul 2008 02:08:40 +0000 (UTC) (envelope-from mldodson@comcast.net) Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by QMTA07.emeryville.ca.mail.comcast.net with comcast id t9Qk1Z05m0cQ2SLA7Dsanh; Wed, 23 Jul 2008 01:52:34 +0000 Received: from wotan.mlandml.net ([98.198.9.238]) by OMTA10.emeryville.ca.mail.comcast.net with comcast id tDsJ1Z00C588yLJ8WDsKft; Wed, 23 Jul 2008 01:52:20 +0000 X-Authority-Analysis: v=1.0 c=1 a=rXlOLYaVl1EA:10 a=YvDAih6sZXoA:10 a=rITDv7nW5hcA:10 a=cOYuRaPrs3txQUr7vgIA:9 a=fT7zWUTO5mdtrjFWkDgA:9 a=QQ-F_myUZZaFvbKKUrYk9A3lgXsA:4 a=UPcRQpLWhfcA:10 Message-ID: <48868EE0.3090806@comcast.net> Date: Tue, 22 Jul 2008 20:52:32 -0500 From: "M. L. Dodson" User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Martin Tournoij , Edwin Groothuis , ports@freebsd.org References: <48866FDF.9030903@comcast.net> In-Reply-To: <48866FDF.9030903@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 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: Wed, 23 Jul 2008 02:08:40 -0000 M. L. Dodson wrote: > 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 I just discovered the port depends on a 64-bit. Work around the patch rejection to get it to work on 32-bit, and I will fix it tomorrow. -- M. L. Dodson Email: mldodson-at-comcast-net Phone: eight_three_two-five_63-386_one