>Number:         23078
>Category:       pkg
>Synopsis:       net/tightvnc using wrong make under Linux
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 07 04:54:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        Linux
>Organization:
http://bsd.reedmedia.net/
>Environment:
>Description:
Building pkgsrc/net/tightvnc under Linux fails:

make includes
including in ./include...
make: invalid option -- C
Usage: make [-Beiknqrst] [-D variable] [-d flags] [-f makefile]
            [-I directory] [-j max_jobs] [-m directory] [-V variable]
            [variable=value] [target ...]
*** Error code 2

This is the error from bmake. 

The work/vnc_unixsrc/Xvnc/include/Makefile made from the Imake has:
    MAKE = make

And a few places with:
$(MAKE) -C $$i $(MFLAGS) $(PARALLELMFLAGS) DESTDIR=$(DESTDIR) ...

>How-To-Repeat:
	
>Fix:
I don't know why it is using bmake here. My "make" is gmake.
net/tightvnc/Makefiles doesn't say to use GMAKE.

I guess one fix would be to use USE_GMAKE for Linux OPSYS. It works for me.
(tightvnc's vncserver works under Linux.)

But under NetBSD, it uses bmake style (even if USE_GMAKE), like:
(cd $$i && $(MAKE) $(MFLAGS) $(PARALLELMFLAGS) ... 

Maybe it would be better to make it use correct syntax for bmake?

Then again, patch-aa uses "make" instead of ${MAKE} a few times.
>Release-Note:
>Audit-Trail:
>Unformatted: