While running emerge gnome 1106203553: Started emerge on: Jan 19, 2005 22:45:53 1106203553: *** emerge gnome 1106203567: >>> emerge (1 of 150) app-admin/fam-2.7.0-r2 to / 1106203567: === (1 of 150) Cleaning (app-admin/fam-2.7.0-r2::/usr/portage/app-a dmin/fam/fam-2.7.0-r2.ebuild) Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed I tried find / -name fam.o.lock and find / -name Client.o.lock and nothing was found, any ideas? Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: /bin/sed: -e expression #1, char 21: unknown command: `/' /bin/sed: -e expression #1, char 21: unknown command: `/' Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed Waiting for fam.o.lock to be removed I had to cancel after it ran for several hours
I also tried compiling xscreensaver by itself, i hopes that xscreensaver would then help gnome, but you can see the results below. emerge xscreensaver Calculating dependencies ...done! >>> emerge (1 of 22) media-libs/svgalib-1.9.19-r1 to / >>> Downloading http://gentoo.osuosl.org/distfiles/svgalib-1.9.19.tar.gz --22:54:46-- http://gentoo.osuosl.org/distfiles/svgalib-1.9.19.tar.gz => `/usr/portage/distfiles/svgalib-1.9.19.tar.gz' Resolving gentoo.osuosl.org... failed: Temporary failure in name resolution. >>> Downloading http://cudlug.cudenver.edu/gentoo/distfiles/svgalib-1.9.19.tar.gz --22:55:26-- http://cudlug.cudenver.edu/gentoo/distfiles/svgalib-1.9.19.tar.gz => `/usr/portage/distfiles/svgalib-1.9.19.tar.gz' Resolving cudlug.cudenver.edu... failed: Temporary failure in name resolution. >>> Downloading ftp://mirrors.tds.net/gentoo/distfiles/svgalib-1.9.19.tar.gz --22:56:06-- ftp://mirrors.tds.net/gentoo/distfiles/svgalib-1.9.19.tar.gz => `/usr/portage/distfiles/svgalib-1.9.19.tar.gz' Resolving mirrors.tds.net... failed: Temporary failure in name resolution. >>> Downloading ftp://gentoo.ccccom.com/distfiles/svgalib-1.9.19.tar.gz --22:56:46-- ftp://gentoo.ccccom.com/distfiles/svgalib-1.9.19.tar.gz => `/usr/portage/distfiles/svgalib-1.9.19.tar.gz' Resolving gentoo.ccccom.com... failed: Temporary failure in name resolution. >>> Downloading http://www.arava.co.il/matan/svgalib/svgalib-1.9.19.tar.gz --22:57:27-- http://www.arava.co.il/matan/svgalib/svgalib-1.9.19.tar.gz => `/usr/portage/distfiles/svgalib-1.9.19.tar.gz' Resolving www.arava.co.il... failed: Temporary failure in name resolution. !!! Couldn't download svgalib-1.9.19.tar.gz. Aborting.
your 'emerge info' ? (like you always should provide -> read the bugreport form)
xscreensaver failure clearly indicates your internet connectivity was down, and is irrelevant. Please post your emerge info.
Here is the emerge info, sorry. emerge info Portage 2.0.51-r14 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 02:42:32)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r2, 1.6.3, 1.7.9, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r3 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=pentium3 -fomit-frame-pointer -fPIC -pipe" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=pentium3 -fomit-frame-pointer -fPIC -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://cudlug.cudenver.edu/gentoo/ ftp://mirrors.tds.net/gentoo ftp://gentoo.ccccom.com" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X Xaw3d alsa apm arts avi berkdb bitmap-fonts bootsplash bzlib cdr crypt cups dvd encode esd f77 fam font-server foomaticdb fortran gdbm gif gnome gpm gssapi gtk gtk2 imlib ipv6 jpeg kde kerberos libg++ libwww mad mikmod motif mpeg ncurses nls nptl oggvorbis opengl oss pam pcmcia pdflib perl png python qt quicktime readline real samba sdl shared slang spell ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts usb x86 xml2 xmms xprint xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, PORTDIR_OVERLAY
Trying to come up with a fix OUTSIDE of the portage package was a pain, so hopefully a dev can come up with a solution. Here is the culprit: /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib/Makefile calls ../libtool which TRIES to remove both ./.deps/Client.TPlo and ./.deps/fam.TPlo (NOT Client.o.lock and fam.o.lock like it says). Obviously, the problem is, neither of these files exist... only Client.Plo and fam.Plo. Simply opening up another terminal and calling 'touch /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib/Client.TPlo && /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib/fam.TPlo' will get you past the "Waiting for Client.o.lock/fam.o.lock to be removed" message
what if you just downgrade portage to stable ?
It does not resolve the issue.
stable is the wrong word, downgrade it to 2.0.51-r3 & retry.
emerge info Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r12 x86_64) ================================================================= System uname: 2.6.9-gentoo-r12 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 28 2004, 05:17:44)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=k8 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=k8 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ ftp://gentoo.risq.qc.ca/ ftp://gentoo.agsn.ca/ http://gentoo.mirrored.ca/ ftp://gentoo.mirrored.ca/ http://gentoo.osuosl.org/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/home/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi alsa amd64 berkdb bitmap-fonts bonobo cdr crypt cups dbus divx4linux doc dvd dvdr eds esd f77 fam flac font-server foomaticdb fortran gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml imagemagick imlib ipv6 java jp2 jpeg libwww lzw lzw-tiff mozilla multilib ncurses nls nocd nptl offensive oggvorbis opengl oss pam pcre perl png python qt readline samba scanner sdl ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb userlocales xml xml2 xmms xpm xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY This version of portage has been running fine since Jan 24. Trying the touch idea didn't work in my case and I can't find any fam.o or Client.o using # find / -type f -iname 'Client*' -or -iname 'fam*' The make just before the neverending *.lock error is: config.status: creating lib/Makefile config.status: executing depfiles commands make[2]: Leaving directory `/home/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib' make[2]: Entering directory `/home/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib' source='Client.c++' object='Client.lo' libtool=yes \ depfile='.deps/Client.Plo' tmpdepfile='.deps/Client.TPlo' \ depmode=gcc3 /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DFAM_CONF=\"/etc/fam.conf\" -O2 -mtune=k8 -pipe -fomit-frame-pointer -c -o Client.lo `test -f 'Client.c++' || echo './'`Client.c++ source='fam.c++' object='fam.lo' libtool=yes \ depfile='.deps/fam.Plo' tmpdepfile='.deps/fam.TPlo' \ depmode=gcc3 /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DFAM_CONF=\"/etc/fam.conf\" -O2 -mtune=k8 -pipe -fomit-frame-pointer -c -o fam.lo `test -f 'fam.c++' || echo './'`fam.c++ Waiting for fam.o.lock to be removed Waiting for Client.o.lock to be removed
Reverting automake-1.5 to 1.4_p6 allowed fam to correctly emerge.(glsa-check -f all sorted it for me)
Same problem solved here: For to be determined reasons, /usr/bin/automake had disappeared before/does not exist. Emerging autoconf-wrapper does this symlink reapear. Now I can successfully emerge fam. * sys-devel/autoconf : [ I] 2.13 (2.1) [ ] 2.59-r5 (2.5) [ I] 2.59-r6 (2.5)
thats more of a lead, so there had been some trouble with the auto* stuff causing this..
base-sys got any clues on what happened to cause comment #11 & #10 ?
ive seen one portage bug so far where automake wasnt updated properly ... and another one or two where a user's system didnt pull in all the new autoconf/automake versions, but we werent able to recreate the bug on the user's systems once we tried i'd suggest just making sure you have 2 versions of autoconf and 6 versions of automake, plus the auto{make,conf}-wrapper packages on your system
Having only 4 automake versions, * sys-devel/automake : [ I] 1.4_p6 (1.4) [ ] 1.5 (1.5) [ I] 1.6.3 (1.6) [ ] 1.7.9-r1 (1.7) [ I] 1.8.5-r1 (1.5) [ ] 1.8.5-r3 (1.8) [ I] 1.9.4 (1.9) But have a look at Bug #80344 same underlying reason...
Created attachment 50760 [details, diff] fam-2.7.0-r2.ebuild.diff Please apply attached patch to fam-2.7.0-r2.ebuild. - It hasn't compiled with the dnotify patch, commented it out. - Doesn't use lock files any more, precautions taken that it compiles only one file a time Output of emerge info, if someone wants to figure it out> Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r6 x86_64) ================================================================= System uname: 2.6.10-gentoo-r6 x86_64 Mobile AMD Athlon 64 Processor 2800+ Gentoo Base System version 1.5.3 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 7 2005, 09:47:43)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.9.4, 1.8.5-r3, 1.4_p6, 1.6.3, 1.7.9, 1.5 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac aalib accessibility acpi alsa audiofile bash-completion berkdb bitmap-fonts blender-game bluetooth bonobo bzlib c++ cairo cddb cdparanoia cdr cgi cjk cross crypt cups directfb divx4linux doc dri dvd dvdr dvdread edl emacs emacs-w3 encode esd ethereal ex f77 fam fbcon fftw flac flash flatfile font-server fortran ftp gd gdbm gif ginac glx gmp gnome gphoto2 gpm gstreamer gtk gtkhtml imagemagick imap imlib insecure-drivers ipv6 java javascript jp2 jpeg kde lcms leim libwww lirc lzw lzw-tiff mad mbox mikmod mime mng motif mozilla mpi mule multilib mysql ncurses nls offensive oggvorbis opengl oss pam pcntl pcre perl php png pnp ppds python qt readline recode samba sdk sdl sharedmem simplexml slang ssl svg sysvipc tcltk tcpd tetex theora tiff tokenizer truetype truetype-fonts type1-fonts unicode usb userlocales v4l v4l2 vhosts videos wmf xfs xine xinerama xml xml2 xmms xosd xpm xprint xrandr xv xvid xvmc yv12 zlib video_cards_radeon linguas_en linguas_de" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
afaics the problem here is the auto* transition to SLOTs and not fam, closing it as such.
Bug still exists in stable AMD64, 2005-02-19.. Applied suggested patch and it works fine. Will this patch be applied to the distribution soon?
Regarding Comment #17 This is not an auto* problem, this auto* problem was the first problem, but once solved, still had this lock problem. Please apply the patch. Jairo, can you reopen this bug? Thanks....
I can't rep it, the patch is just a workaround. I want to know why it happens in a few cases only.
This happens, if you have -j2 (or greater) in MAKEOPTS in /etc/make.conf
I've just hit this problem, just a note to say that the patch above solved it for me.
The cause is CFLAGS - at least for me. To trace back to the cause: libtool(1197): if test "$need_locks" = yes; then until $run ln "$srcfile" "$lockfile" 2>/dev/null; do $show "Waiting for $lockfile to be removed" sleep 2 done libtool(1184): if test "$compiler_c_o" = no; then ... else output_obj= need_locks=no libtool(149): # Does compiler simultaneously support -c and -o options? compiler_c_o="no" # Must we lock files when doing compilation ? need_locks="yes" configure(6580): # The compiler can only warn and ignore the option if not recognized # So say no if there are warnings if test ! -s out/conftest.err; then lt_cv_prog_compiler_c_o=yes Removing the item that was causing a warning from my CFLAGS caused the problem to go away. The pertinent test for me is: echo "int some_variable = 0;" > conftest.c $mygcc -c $CFLAGS -o conftest.o conftest.c If the above doesn't solve everybody else's problems, attaching config.log plus the output of the following would be helpful: grep -E '^(compiler_c_o|need_locks)' libtool
*** Bug 89513 has been marked as a duplicate of this bug. ***
*** Bug 89866 has been marked as a duplicate of this bug. ***
I don't see this as a gnome-related problem but more generally a libtool problem. Adding media-video to cc as two problems were with media-video packages.
I was recieving the "Waiting for Client.o.lock to be removed" problem until I specifically `emerge =sys-devel/automake-1.6.3` Presumably the problem is caused by the dnotify patch. The patch specifically notes that you must re-autogen after the patch is applied <http://archives.linuxfromscratch.org/mail-archives/patches/2003-October/000375.html>. If automake-1.6 is not installed, the re-automake fails, but the build continues anyway. With automake-1.6 installed, I no longer recieved the lock problems. In regards to comment #21, I use MAKEOPTS="-j1" and still got the lock file problems (although they were not interleaved; 'Client.o.lock' came first, and 'fam.lock.o' came later only if manually touched the build past Client.o.lock) As a correction to comment #5, the touching should take place in 'lib/.deps/', not in 'lib/': sudo -u portage touch /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/lib/.deps/{Client,fam}.TPlo
I'm running two gentoo systems, my laptop and a htpc/server. Both running 2005.0. Server is a stage 1, laptop a stage 2 install, both running distcc with the other. I built and installed fam as a dependency to gnome on both systems. Both were configured with -j5 and, as previously noted, distcc. The laptop produced no errors at all. The server suffered from the bug as described. Here's some information which is far from fixing it, but might help others narrow it down. First thing I tried was searching for the lock files as well -- they don't exist. Second was once the bug presented itself in emerge, SIGINT, then cd to /var/tmp/portage/fam-2.7.0-r4/work/fam-2.7.0 and poke around. I ended up going into each directory and running "make" to help narrow the problem. As we already know, the problem solely exists in the lib directory. However, here is some additional info: First, I ran "make clean" in the lib dir. Then "make". Prompty it produces 1 command and sticks with a slightly different behavior. Instead of flooding the screen with messages of two non-existant lock files, it instead only talks about "Client.o.lock". So I killed make, copied the command it spit out and ended up failing on and ran it bare in the shell. It compiled, no error. Re-run make... now it starts complaining about "fam.o.lock". So I repeat it, and then "make" goes through without a hitch. I proceed to build the entire package without incident from the root work directory. Now, I don't like fancy tricks of 'injecting' packets with emerge, so at this point I confirmed that something is going on with automake. So I disabled distcc to see what that did -- but, being lazy, I left the -j5 in the makeopts. Once distcc was removed from make.conf, the package compiled without a hitch. This would seem all clean and cut -- distcc can't compile it and all. But then, distcc compiled it fine on my laptop. Both systems run automake-1.9.5 for the record. I'm happy to provide any other details on this reproducable bug that appears only on one of my two systems.
*** Bug 79699 has been marked as a duplicate of this bug. ***
This bug is present in stable systems and prevents installs.
Check the cflags, 90% there's an invalid cflags that is causing this. Look at autoconf result for "whether compiler supports -o flag".
In my case, this problem was solved by installing automake-1.6 In fact, if this version isn't installed, a small error appears and next, the message : Waiting for Client.o.lock to be removed
*** Bug 114006 has been marked as a duplicate of this bug. ***
From the sounds of it, we just need to ensure automake-1.6.* is installed, and there shouldn't be an issue. Is adding this exact dep to fam evil, or can we fix it to work with newer versions of automake as well?
*** Bug 115672 has been marked as a duplicate of this bug. ***
(In reply to comment #34) > From the sounds of it, we just need to ensure automake-1.6.* is installed, and > there shouldn't be an issue. Is adding this exact dep to fam evil, or can we > fix it to work with newer versions of automake as well? Then at least Bug 89866, Bug 89513 and Bug 115672 are not duplicates of this one, because those people do have automake-1.6* installed. Bug 115672 suggests that this issue occurs when PORTAGE_TMPDIR is on separate partition. Hmmm...
*** Bug 94427 has been marked as a duplicate of this bug. ***
old bug
