Date: Sun, 20 Nov 2005 13:04:01 +0200 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Sam Lawrance <boris@brooknet.com.au> Cc: Jose Alonso Cardenas Marquez <jacardenasm@gmail.com>, freebsd-ports@freebsd.org Subject: Re: OPTIONS with PKGNAMEPREFIX, dont work? Message-ID: <20051120130401.244bea2e@it.buh.tecnik93.com> In-Reply-To: <24405BE9-B7AD-4FE5-9977-7DC45753DA0D@brooknet.com.au> References: <7c58fcfc0511191016t553859a1g@mail.gmail.com> <24405BE9-B7AD-4FE5-9977-7DC45753DA0D@brooknet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Nov 2005 18:03:14 +1100
Sam Lawrance <boris@brooknet.com.au> wrote:
>
> 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)
Yes, this is an old and annoying one.
--
IOnut - Unregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
BOFH excuse #272:
Netscape has crashed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051120130401.244bea2e>