Date: Sat, 07 Jan 2006 18:50:41 +0900 From: KOMATSU Shinichiro <koma2@lovepeers.org> To: Stijn Hoop <stijn@win.tue.nl> Cc: Jeremy Messenger <mezz7@cox.net>, Doug Barton <dougb@freebsd.org>, freebsd ports <freebsd-ports@freebsd.org> Subject: Re: New /bin/sh based script to manage ports Message-ID: <43BF8EF1.3000005@lovepeers.org> In-Reply-To: <20060107092614.GH79296@pcwin002.win.tue.nl> References: <43BCF31F.8050900@FreeBSD.org> <op.s2w24xlg9aq2h7@mezz.mezzweb.com> <43BF7F8D.6080809@FreeBSD.org> <20060107092614.GH79296@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Stijn Hoop wrote:
> On Sat, Jan 07, 2006 at 12:45:01AM -0800, Doug Barton wrote:
>
>>However, the other two present a chicken and
>>egg problem if I choose to use 'make -V' to get the values of these
>>variables (where do I cd to?).
>
>
> Why do you need to cd?
>
> [stijn@tangaloor] </tmp> ls Makefile
> ls: Makefile: No such file or directory
> [stijn@tangaloor] </tmp> make -V PORTSDIR
> /net/freebsd/ports
PORTSDIR is set in bsd.port.mk, which is not included
if you do not explicitly include it by ".include <bsd.port.mk>".
Don't you set it in /etc/make.conf or environment variable?
Recently I thought the same problem, and
the best solution I came up with till now is
running the following command:
% echo '.include <bsd.port.mk>' | make -f - -V PORTSDIR
I will add this into portupgrade in later release
(after solving the MOVED problem...).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43BF8EF1.3000005>