Date: Wed, 23 Jul 2008 08:19:53 -0500 From: "M. L. Dodson" <mldodson@comcast.net> To: Martin Tournoij <carpetsmoker@rwxrwxrwx.net>, Edwin Groothuis <edwin@mavetju.org>, ports@freebsd.org Subject: Re: Help for a problematic port to replace biology/nab Message-ID: <48872FF9.9040907@comcast.net> In-Reply-To: <48868EE0.3090806@comcast.net> References: <48866FDF.9030903@comcast.net> <48868EE0.3090806@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
M. L. Dodson wrote: > 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. > The port (same location, same name) has been updated to handle both 64-bit and 32-bit systems. Did a cleanup edit that was ill advised. Thanks for the help. Bud Dodson -- M. L. Dodson Email: mldodson-at-comcast-net Phone: eight_three_two-five_63-386_one
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48872FF9.9040907>