Date: Tue, 28 Jun 2005 14:35:31 +0200 From: Thierry Herbelot <thierry@herbelot.com> To: Jose M Rodriguez <josemi@freebsd.jazztel.es> Cc: ports@freebsd.org, freebsd-ports@freebsd.org Subject: Re: bug in patching phase of cups-pstoraster Message-ID: <200506281435.33658.thierry@herbelot.com> In-Reply-To: <200506281337.07507.josemi@redesjm.local> References: <200506281236.08334.thierry@herbelot.com> <200506281337.07507.josemi@redesjm.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Tuesday 28 June 2005 13:37, Jose M Rodriguez a écrit :
> El Martes, 28 de Junio de 2005 12:36, Thierry Herbelot escribió:
> > Hello,
> >
> > I have here a R/O shared ports tree, under the /files2 mount point. A
> > symbolic link points from /usr/ports to /files2/ports
>
> This is not enough. You must define PORTSDIR.
This is indeed a work-around, but this is the first port where I saw this kind
of problem (and I have some *hundreds* of ports which build correctly without
setting PORTSDIR).
This is an explanation :
in ports/Mk/bsd.port.mk, WRKDIR is correctly set with :
WRKDIR?= ${WRKDIRPREFIX}${.CURDIR}/work
but in ports/print/cups-pstoraster/Makefile, the new WRKSRC is hardwired to :
${WRKDIRPREFIX}${PORTSDIR}/${GHOSTSCRIPT_PORT}/work/ghostscript
which is wrong as PORTSDIR points (correctly) to /usr/ports when ${.CURDIR}
is /files2/ports
for the time being, I will set PORTSDIR.
*thanks* for the quick answer
cheers
TfH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506281435.33658.thierry>