From owner-freebsd-ports@FreeBSD.ORG Wed Jul 23 01:31:28 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 4C6861065670 for ; Wed, 23 Jul 2008 01:31:28 +0000 (UTC) (envelope-from carpetsmoker@rwxrwxrwx.net) Received: from mail.rwxrwxrwx.net (rwxrwxrwx.net [82.93.23.199]) by mx1.freebsd.org (Postfix) with ESMTP id E4E908FC15 for ; Wed, 23 Jul 2008 01:31:27 +0000 (UTC) (envelope-from carpetsmoker@rwxrwxrwx.net) Received: from localhost (localhost [127.0.0.1]) by mail.rwxrwxrwx.net (Postfix) with ESMTP id 4991E6D409; Wed, 23 Jul 2008 03:19:34 +0200 (CEST) Received: from mail.rwxrwxrwx.net ([127.0.0.1]) by localhost (mail.rwxrwxrwx.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cp40WTGtHONg; Wed, 23 Jul 2008 03:19:29 +0200 (CEST) Received: from rwxrwxrwx.net (phong [192.168.100.13]) by mail.rwxrwxrwx.net (Postfix) with ESMTPSA id 9A39F6D442; Wed, 23 Jul 2008 03:19:29 +0200 (CEST) Date: Wed, 23 Jul 2008 03:15:57 +0200 From: Martin Tournoij To: "M. L. Dodson" Message-ID: <20080723011557.GA4359@rwxrwxrwx.net> Mail-Followup-To: "M. L. Dodson" , ports@freebsd.org References: <48866FDF.9030903@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <48866FDF.9030903@comcast.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: ports@freebsd.org 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 List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2008 01:31:28 -0000 On Tue, Jul 22, 2008 at 06:40:15PM -0500, 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. What a very odd build system... Could you attach the port, so I/we can have a look at this AmberTools (and it's build system). -- Martin Tournoij carpetsmoker@rwxrwxrwx.net http://www.daemonforums.org QOTD: You will have long and healthy life.