Date: Wed, 23 Jul 2008 03:15:57 +0200 From: Martin Tournoij <carpetsmoker@rwxrwxrwx.net> To: "M. L. Dodson" <mldodson@comcast.net> Cc: ports@freebsd.org Subject: Re: Help for a problematic port to replace biology/nab Message-ID: <20080723011557.GA4359@rwxrwxrwx.net> In-Reply-To: <48866FDF.9030903@comcast.net> References: <48866FDF.9030903@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080723011557.GA4359>