Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Jul 2013 10:31:15 +0300
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Tijl Coosemans <tijl@coosemans.org>
Cc:        freebsd-toolchain@FreeBSD.org, freebsd-ports@FreeBSD.org, FreeBSD Current <freebsd-current@FreeBSD.org>
Subject:   Re: new make vs security/vpnc
Message-ID:  <51DBBC43.5040703@FreeBSD.org>
In-Reply-To: <51DBBAD8.7070502@coosemans.org>
References:  <51DB2A10.2030700@FreeBSD.org> <51DB2CEE.2040504@FreeBSD.org> <51DB37AA.1050206@FreeBSD.org> <51DBBAD8.7070502@coosemans.org>

next in thread | previous in thread | raw e-mail | index | archive | help
on 09/07/2013 10:25 Tijl Coosemans said the following:
> On 2013-07-09 00:05, Andriy Gapon wrote:
>> Seems like the problem boils down to this:
>> 
>> $ make -V MAKEFILE /usr/ports/security/vpnc/Makefile $ fmake -V MAKEFILE 
>> Makefile
>> 
>> The only explicit assignments of MAKEFILE that I could find in ports 
>> infrastructure are these: /usr/ports/Mk/bsd.port.mk:MAKEFILE?=
>> Makefile /usr/ports/Mk/bsd.gnustep.mk:MAKEFILE=  GNUmakefile
> 
> The problem is probably that .OBJDIR (/usr/obj/usr/ports/security/vpnc) 
> exists. Bmake assigns an absolute path to MAKEFILE in that case.

Bingo!
I use WRKDIRPREFIX=/usr/obj/*ports*, so i am not sure how
/usr/obj/usr/ports/security/vpnc came to exist.  A timestamp on it is 1 year
old, so I won't be able to recall now.
Thank you!

> MAKEFILE is an internal variable of make and bsd.port.mk uses it for
> another purpose. It should use another name like MAKE_FILE imho.

I agree.

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51DBBC43.5040703>