pkg/34009: comms/minicom configure fails on MacOS X 10.4.7

[jdbaker%mylinuxisp.com@localhost]

>Number:         34009
>Category:       pkg
>Synopsis:       comms/minicom configure fails on MacOS X 10.4.7
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 16 05:05:00 +0000 2006
>Originator:     John D. Baker
>Release:        MacOS X 10.4.7, pkgsrc-2006Q2
>Organization:
>Environment:
Darwin bwg3.technoskunk.fur 8.7.0 Darwin Kernel Version 8.7.0: Fri May 26 
15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC Power Macintosh powerpc

>Description:
Building comms/minicom on MacOS X 10.4.7 fails during the configuration
phase as follows:

[...]
checking for com line lock directory... configure: error: No suitable lock 
directory
*** Error code 1

Stop.
bmake: stopped in /usr/pkgsrc/comms/minicom
[...]

>How-To-Repeat:
Attempt to build comms/minicom on MacOS X 10.4.7.
>Fix:
The default behavior is to check a number of common locations.
None of them exist on MacOS X 10.4.7, though.

Workaround:

sudo mkdir -p /path/to/lockdir
CONFIGURE_ARGS=--enable-lock-dir=/path/to/lockdir bmake install
sudo chown uucp:dialer /path/to/lockdir

MacOS X 10.3.9 (earlier versions?) appear to have at least one of the
directories otherwise searched for and is not affected during building
or installation.  There may be a problem the first time an unpriviledged
user runs minicom because it runs SUID uucp while the lock-dir is owned
by root:wheel with mode 755. In which case, one may work around it by
chown-ing it to uucp:dialer, or other strategy (mode 777 with sticky bit?)