public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-dev List <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] nautilus compile stuck in loop
Date: 03 May 2002 14:31:53 +0800	[thread overview]
Message-ID: <1020407513.7754.72.camel@rattus> (raw)

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 .. \




             reply	other threads:[~2002-05-03  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03  6:31 Bill Kenworthy [this message]
2002-05-03 14:41 ` [gentoo-dev] nautilus compile stuck in loop Terje Kvernes
2002-05-03 15:10   ` Bill Kenworthy
2002-05-03 16:06     ` Matthew J. Turk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1020407513.7754.72.camel@rattus \
    --to=billk@iinet.net.au \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox