OPTIONS with PKGNAMEPREFIX, dont work?

[Jose Alonso Cardenas Marquez]

I solve it, using OPTIONSFILE

example:

PORT_DBDIR?=    /var/db/ports
LATEST_LINK=    py-${PORTNAME}
OPTIONSFILE?=   ${PORT_DBDIR}/${LATEST_LINK}/options

Greetings
ACM



2005/11/20, Ion-Mihai Tetcu <itetcu at people.tecnik93.com>:
> On Sun, 20 Nov 2005 18:03:14 +1100
> Sam Lawrance <boris at 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
>
>
>