NetBSD Problem Report #34009

From  Sun Jul 16 05:02:12 2006
Return-Path: <>
Received: by (Postfix, from userid 31301)
	id 6C3CC63B896; Sun, 16 Jul 2006 05:02:12 +0000 (UTC)
Message-Id: <>
Date: Sun, 16 Jul 2006 05:02:12 +0000 (UTC)
Subject: comms/minicom configure fails on MacOS X 10.4.7
X-Send-Pr-Version: www-1.0

>Number:         34009
>Category:       pkg
>Synopsis:       comms/minicom configure fails on MacOS X 10.4.7
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    schmonz
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 16 05:05:00 +0000 2006
>Last-Modified:  Tue Jan 01 22:51:55 +0000 2008
>Originator:     John D. Baker
>Release:        MacOS X 10.4.7, pkgsrc-2006Q2
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

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

bmake: stopped in /usr/pkgsrc/comms/minicom

Attempt to build comms/minicom on MacOS X 10.4.7.
The default behavior is to check a number of common locations.
None of them exist on MacOS X 10.4.7, though.


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?)



Responsible-Changed-From-To: pkg-manager->darwin-pkg-people
Responsible-Changed-When: Sun, 16 Jul 2006 07:24:37 +0000
Darwin pkgsrc PR.

Responsible-Changed-From-To: darwin-pkg-people->schmonz
Responsible-Changed-When: Wed, 30 May 2007 09:44:11 +0000
I'll handle this one.

State-Changed-From-To: open->feedback
State-Changed-When: Wed, 30 May 2007 09:44:11 +0000
Awaiting feedback.

From: Amitai Schlair <>
To: "John D.Baker" <>,
Subject: Re: pkg/34009
Date: Wed, 30 May 2007 05:43:40 -0400

 minicom packages for me on 10.4.9 (Intel). Is this still an issue?

From: John D.Baker <>
Cc: John D.Baker <>,
Subject: Re: pkg/34009
Date: Tue, 12 Jun 2007 11:09:33 -0500

 As of pkgsrc-current, the problem described in this PR still exists
 on MacOS X 10.4.x (PPC).  The proposed workaround is still required
 in order for the configure step to complete.

 MacOS X 10.3.9 and 10.2.8 have a lock directory (/var/spool/lock)
 by default, so they do not have this problem.  It may be necessary
 to chown the lock directory to "uucp:dialer" or set the mode to 1777
 before running minicom as an unprivileged user the first time, however.

 John D. Baker                            NetBSD     Darwin/MacOS X
 http://mylinuxisp(dot)com/(tilde)jdbaker/     OpenBSD            FreeBSD
 BSD.  It just sits there and _works_.
 GPG fingerprint = D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

State-Changed-From-To: feedback->open
State-Changed-When: Tue, 01 Jan 2008 22:51:55 +0000
Feedback provided.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.