Date: Sun, 20 Nov 2005 18:03:14 +1100 From: Sam Lawrance <boris@brooknet.com.au> To: Jose Alonso Cardenas Marquez <jacardenasm@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: OPTIONS with PKGNAMEPREFIX, dont work? Message-ID: <24405BE9-B7AD-4FE5-9977-7DC45753DA0D@brooknet.com.au> In-Reply-To: <7c58fcfc0511191016t553859a1g@mail.gmail.com> References: <7c58fcfc0511191016t553859a1g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20/11/2005, at 5:16 AM, Jose Alonso Cardenas Marquez wrote:
> Hi,
>
> I'm using OPTIONS with PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} into
> Makefile, but it's not working, and display this message
>
> ===> Using wrong configuration file /path/options/file
>
> If i comment PKGNAMEPREFIX, this works.
>
> the question is, OPTIONS with PKGNAMEPREFIX, dont work?
>
What port? Can you put it up somewhere and describe how to repeat the
problem?
I ran into a related (though probably different) problem the other
day - if you use an OPTIONS-based knob to change the value of
PKGNAMEPREFIX, a port build will fail after the first config due to
changed cookie names.
(ie. the files like ${WRKDIR}/.build_doneXXXX)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24405BE9-B7AD-4FE5-9977-7DC45753DA0D>