[MacPorts] #45992: selfupdate from 2.2.0 to 2.3.3 taking over a day to run
MacPorts
noreply at macports.org
Sun Nov 23 17:03:41 PST 2014
#45992: selfupdate from 2.2.0 to 2.3.3 taking over a day to run
------------------------+--------------------------------
Reporter: cfdollak@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.3
Keywords: selfupdate | Port:
------------------------+--------------------------------
I am running OSX 10.9.5, Xcode 4.6.3. I started running sudo port -v
selfupdate about 32 hours ago. It ran up to
{{{
===> making all in src/darwintracelib1.0
/usr/bin/cc -g -O2 -std=c99 -Wextra -Wall -fPIC -arch x86_64 -arch i386
-DHAVE_CONFIG_H
-I/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base/src
-I/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base/src
-I.
-I/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base/vendor
/vendor-destroot//opt/local/libexec/macports/include -c -o access.o
access.c
}}}
fairly quickly, but has been stuck there ever since. It's mostly been
running xcrun during that time, but it occasionally switches to something
else and back to xcrun before I can see what it's doing. The xcrun process
generally isn't taking up more than 20% of my CPU. Attached is a spindump,
in case that helps identify the problem.
--
Ticket URL: <https://trac.macports.org/ticket/45992>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list