Different interpretation of PATH_KRB5_CONFIG between make and portmaster

[Dewayne Geraghty]

I'm a little perplexed.  I can build the new port security/kstart using
make, but not portmaster.  The latter seems to substitute the value for
PATH_KRB5_CONFIG.

I use port security/heimdal for all ports so I added to the Makefile file
PATH_KRB5_CONFIG=       /usr/local/bin/krb5-config

When I build a package using make, as follows:
rm -R /var/ports/usr/ports/* /usr/staging/*
cd /usr/ports/security/kstart && make -DBATCH clean deinstall package
the package is built and examining the log file, the build log  uses
krb5-config... /usr/local/bin/krb5-config

while
rm -R /var/ports/usr/ports/* /usr/staging/*
portmaster --no-term-title --no-confirm -H -K -D -g -G -B -v 
security/kstart
substitute's the Makefiles krb5-config path with
"checking for krb5-config... /usr/bin/krb5-config"
and fails.

However, being tenacious, this also succeeds in building a package
portmaster --no-term-title --no-confirm -H -K -D -g -G -B -v -m
PATH_KRB5_CONFIG=/usr/local/bin/krb5-config security/kstart

Can anyone advise the different interpretation by make &/or portmaster
of PATH_KRB5_CONFIG which I identified by kstart's
./configure --help

The system is a FreeBSD 10.1-STABLE #0 r278144M: Wed Feb  4 05:08:40
AEDT 2015 using i386

Regards, Dewayne
PS The arguments to portmaster is an extract from a larger configure
script. 

-- 
For the talkers: “The superior man acts before he speaks, and afterwards speaks according to his action.”
For everyone else: “Life is really simple, but we insist on making it complicated.”