Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 84028 - Minicom Emerge Failed on com line lock directory
Summary: Minicom Emerge Failed on com line lock directory
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo Dialup Developers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-03 19:36 UTC by Shawn Begin
Modified: 2005-03-05 00:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
The config.log that the error asked me to submit. (config.log,85.48 KB, text/x-log)
2005-03-03 19:39 UTC, Shawn Begin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Begin 2005-03-03 19:36:33 UTC
When I went to emerge Minicom on a fresh install of gentoo on my new to me laptop I ran into a problem on it securing a lock directory during the configure part of making it.

Here is the line:checking for getopt_long... yes
checking for long file names... yes
checking for com line lock directory... configure: error: No suitable lock directory

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/minicom-2.1-r1/work/minicom-2.1/config.log

!!! ERROR: net-dialup/minicom-2.1-r1 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.






Reproducible: Always
Steps to Reproduce:
1. emerge minicom
2.
3.

Actual Results:  
Same thing. I have tried this a few times on this particular machine.

Expected Results:  
the ./configure to finish and the make to begin.

Here is my emerge info:

localhost / # emerge info
Portage 2.0.51.18 (default-linux/x86/2005.0, gcc-3.4.3-20050110,
glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r7 i586)
=================================================================
System uname: 2.6.10-gentoo-r7 i586 AMD-K6(tm) 3D processor
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Feb 23 2005, 08:05:50)]
dev-lang/python:     2.3.5
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r3
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe"
CHOST="i586-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://192.168.0.101"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://192.168.0.101/gentoo-portage"
USE="x86 X aac acpi alsa apm avi berkdb bitmap-fonts bzip2 crypt cups curl
emboss encode f77 fam flac foomaticdb fortran gdbm gif gnome gpm gstreamer gtk
gtk2 imagemagick imlib ipv6 java jpeg libg++ libwww mad mikmod mng motif mozilla
mp3 mpeg ncurses nls nptl oggvorbis opengl oss pam pdflib perl png ppds python
quicktime readline real samba sdl spell ssl tcpd tiff truetype truetype-fonts
type1-fonts wlan xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

Also I have attached the log file as the error has told me to.

If it matters, the modem is a winmodem I used ltmodem as its driver.
Also, I am running udev with the default settings as emerged.

If you need any more information, please do let me know, as this is my first
Gentoo bug.
Comment 1 Shawn Begin 2005-03-03 19:39:39 UTC
Created attachment 52611 [details]
The config.log that the error asked me to submit.
Comment 2 Alin Năstac (RETIRED) gentoo-dev 2005-03-04 02:50:17 UTC
Do you have /var/lock/subsys on that machine?
It should be created by sys-apps/baselayout.
Comment 3 Shawn Begin 2005-03-04 12:26:04 UTC
Actually,

There is no /var/lock directory at all on this system. It is also evident since on bootup I get an error about /var/lock not existing during bootmisc being popped off.

I remerged baselayout and it's fixed now. I can't tell if the bug came from the stage tarball I used (a 2005.0 rc5) or if it was from the bootstrapping.

Anyhow, unless you need any more information from me to perhaps see why this happened, let me know, otherwise, this works fine.

thanks
Shawn
Comment 4 Alin Năstac (RETIRED) gentoo-dev 2005-03-05 00:11:56 UTC
not minicom's problem