[gentoo-user] Emerge is Waiting for lirc_client.o.lock to be removed

2006-01-12 Thread Drew Tomlinson
I've got some weirdness going on with my system after an upgrade.  Seems 
that some things that were compiled with gcc 3.3 don't want to run with 
a kernel that was compiled with gcc 3.4.  I'm not sure of this but 
that's my guess, especially after re-emerging a few packages (that one 
doesn't normally have to re-emerge after a kernel upgrade) and they 
suddenly stop seg faulting.


So anyway, I thought I'd just re-emerge my entire system with 'emerge 
-vuDNe1 world'.  It was chuggin' along fine until it hit 
app-misc/lirc-0.7.2.  The build starts, goes through configure, and 
actually begins compiling, and then starts waiting here:


gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall -c `test -f irxevent.c || echo './'`irxevent.c

`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
source='xmode2.c' object='xmode2.o' libtool=no \
depfile='.deps/xmode2.Po' tmpdepfile='.deps/xmode2.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall -c `test -f xmode2.c || echo './'`xmode2.c

`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
/bin/sh ../libtool --mode=link gcc  -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall   -o irw  irw.o 
Waiting for lirc_client.o.lock to be removed

mkdir .libs
gcc -O2 -mcpu=i686 -fomit-frame-pointer -march=athlon-xp -pipe -Wall -o 
irw irw.o
/bin/sh ../libtool --mode=link gcc  -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall   -o mode2  mode2.o 
gcc -O2 -mcpu=i686 -fomit-frame-pointer -march=athlon-xp -pipe -Wall -o 
mode2 mode2.o
/bin/sh ../libtool --mode=link gcc  -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall   -o irsend  irsend.o 
gcc -O2 -mcpu=i686 -fomit-frame-pointer -march=athlon-xp -pipe -Wall -o 
irsend irsend.o
/bin/sh ../libtool --mode=link gcc  -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall   -o smode2  smode2.o -lvga -lvgagl

Waiting for lirc_client.o.lock to be removed
gcc -O2 -mcpu=i686 -fomit-frame-pointer -march=athlon-xp -pipe -Wall -o 
smode2 smode2.o  -lvga -lvgagl
/bin/sh ../libtool --mode=link gcc  -O2 -mcpu=i686 -fomit-frame-pointer 
-march=athlon-xp -pipe -Wall   -o xmode2  xmode2.o -lSM -lICE -lX11 
gcc -O2 -mcpu=i686 -fomit-frame-pointer -march=athlon-xp -pipe -Wall -o 
xmode2 xmode2.o  -lSM -lICE -lX11

Waiting for lirc_client.o.lock to be removed
Waiting for lirc_client.o.lock to be removed
Waiting for lirc_client.o.lock to be removed
Waiting for lirc_client.o.lock to be removed
Waiting for lirc_client.o.lock to be removed
sandbox:  Caught signal 2 in pid 30088

I've stopped lircd, removed all lirc kernel modules, searched the entire 
file system for a file named lirc_client.o.lock, searched Google for 
the same, even rebooted, and am still stuck at this point.  I keep using 
'emerge --resume' to retry as i don't want to rebuild the 130+ things 
that have already been built.  I just want to continue with the 
remaining 250+.


Any ideas on how to overcome this hurdle?

Thanks,

Drew

--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Emerge is Waiting for lirc_client.o.lock to be removed

2006-01-12 Thread Neil Bothwick
On Thu, 12 Jan 2006 10:45:30 -0800, Drew Tomlinson wrote:

 I've stopped lircd, removed all lirc kernel modules, searched the
 entire file system for a file named lirc_client.o.lock, searched
 Google for the same, even rebooted, and am still stuck at this point.
 I keep using 'emerge --resume' to retry as i don't want to rebuild the
 130+ things that have already been built.  I just want to continue with
 the remaining 250+.
 
 Any ideas on how to overcome this hurdle?

The short term fix is to use emerge --resume --skipfirst to continue with
the next package in the list. It (probably) won't help fix the lircd
problem, but it will let you emerge everything else.


-- 
Neil Bothwick

getting performance from an Amiga is like getting water from a sponge,
getting performance from Windows is like getting blood from a stone -
after banging my head against the stone several times I got some blood

Author of Lightwave 3D


signature.asc
Description: PGP signature


Re: [gentoo-user] Emerge is Waiting for lirc_client.o.lock to be removed

2006-01-12 Thread Drew Tomlinson

On 1/12/2006 10:59 AM Neil Bothwick said the following:


On Thu, 12 Jan 2006 10:45:30 -0800, Drew Tomlinson wrote:

 


I've stopped lircd, removed all lirc kernel modules, searched the
entire file system for a file named lirc_client.o.lock, searched
Google for the same, even rebooted, and am still stuck at this point.
I keep using 'emerge --resume' to retry as i don't want to rebuild the
130+ things that have already been built.  I just want to continue with
the remaining 250+.

Any ideas on how to overcome this hurdle?
   



The short term fix is to use emerge --resume --skipfirst to continue with
the next package in the list. It (probably) won't help fix the lircd
problem, but it will let you emerge everything else.
 



Cool.  Thanks for getting me going again.  lirc is working anyway and 
probably doesn't need rebuilding.  Wonder why I didn't see skipfirst?


Drew

--
gentoo-user@gentoo.org mailing list