From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from mons.uio.no (mons.uio.no [129.240.130.14]) by chiba.3jane.net (Postfix) with ESMTP id 8D594AC397 for ; Fri, 3 May 2002 09:41:48 -0500 (CDT) Received: from nommo.uio.no ([129.240.222.179]) by mons.uio.no with esmtp (Exim 2.12 #7) id 173eFn-0003qG-00 for gentoo-dev@gentoo.org; Fri, 3 May 2002 16:41:47 +0200 Received: from terjekv by nommo.uio.no with local (Exim 2.12 #1) id 173eFn-0004eZ-00 for gentoo-dev@gentoo.org; Fri, 3 May 2002 16:41:47 +0200 To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] nautilus compile stuck in loop References: <1020407513.7754.72.camel@rattus> X-URL: http://terje.kvernes.no/ Organization: do you Gentoo? From: Terje Kvernes Date: 03 May 2002 16:41:47 +0200 In-Reply-To: <1020407513.7754.72.camel@rattus> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 1b0c30c7-0896-4a56-84f8-34ada02676ee X-Archives-Hash: 7906675e7c01ecbed05c1e6463e6ab7b Bill Kenworthy writes: > I have been trying to do an "emerge -u world" after an "emerge rsync" > but in nautilus (gnome-base/nautilus/nautilus-1.0.6-r8.ebuild) it keeps > getting stuck in the loop below. > > cd .. \ > && CONFIG_FILES=libnautilus/Makefile CONFIG_HEADERS= /bin/sh > ./config.status > creating libnautilus/Makefile > make[2]: Leaving directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > make[2]: Entering directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > cd .. \ > && CONFIG_FILES=libnautilus/Makefile CONFIG_HEADERS= /bin/sh > ./config.status > creating libnautilus/Makefile > make[2]: Leaving directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > make[2]: Entering directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > cd .. \ > && CONFIG_FILES=libnautilus/Makefile CONFIG_HEADERS= /bin/sh > ./config.status > creating libnautilus/Makefile > make[2]: Leaving directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > make[2]: Entering directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > cd .. \ > && CONFIG_FILES=libnautilus/Makefile CONFIG_HEADERS= /bin/sh > ./config.status > creating libnautilus/Makefile > make[2]: Leaving directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > make[2]: Entering directory > `/var/tmp/portage/nautilus-1.0.6-r8/work/nautilus-1.0.6/libnautilus' > cd .. \ check the date and time on the machine. your clock might be way off and that can make configure rerun. at least that fixed a similar issue for me. -- Terje