I encountered a similar problem with tightvnc under Linux. The 
workaround/fix is to change the definition of  MakeCmd seen by imake 
from "bmake" to make or gmake. I did this by adding a host.def to the 
package that defined this variable. Perhaps there is a better way?

pkgsrc@blackmouse.biz wrote:
>> Number:         36856
>> Category:       pkg
>> Synopsis:       nas compile problem with modular-xorg
>> Confidential:   no
>> Severity:       critical
>> Priority:       medium
>> Responsible:    pkg-manager
>> State:          open
>> Class:          sw-bug
>> Submitter-Id:   net
>> Arrival-Date:   Wed Aug 29 10:30:00 +0000 2007
>> Originator:     Ondrej Tuma
>> Release:        current
>> Organization:
> Blackmouse
>> Environment:
> Linux ip1 2.6.20.1 #3 Thu Mar 8 18:42:01 CET 2007 i686 athlon-4 i386 GNU/Linux
>> Description:
> make includes
> including in ./include...
> usage: bmake [-BeikNnqrstWX] [-D variable] [-d flags] [-f makefile]
>             [-I directory] [-J private] [-j max_jobs] [-m directory] [-T file]
>             [-V variable] [variable=value] [target ...]
> make: *** [includes] Error 2
> *** Error code 2
> 
> i don't know why, but bmake is use in Makefiles in nas :(
> here is full log:
> http://linux.blackmouse.biz/pub/blackmouse-current/i686/pkgstat/20070829.0804/audio/nas/.broken.html
>> How-To-Repeat:
> bmake
>> Fix:
> 


-- 
John R. Shannon, CISSP
Chief Scientist
DSCI, Information Assurance Division
jshannon@dsci-usa.com
john.r.shannon@us.army.mil
shannonjr@NetBSD.org
(208)522-4506