1

I have upgraded to mavericks and I am following the instructions to upgrade MacPorts, but it is taking days to rebuild libgnome-keyring - I stopped it after three days and deleted it from my "myports.txt" file and restarted - and it was reloaded as a dependency and is now in its second day of building.

Is this behaviour normal? Is there a fix if it's not?

update

This is the output...

--->  Computing dependencies for libgnome-keyring
--->  Fetching archive for libgnome-keyring
--->  Attempting to fetch libgnome-keyring-3.10.1_0.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libgnome-keyring
--->  Attempting to fetch libgnome-keyring-3.10.1_0.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/libgnome-keyring
--->  Attempting to fetch libgnome-keyring-3.10.1_0.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/libgnome-keyring
--->  Fetching distfiles for libgnome-keyring
--->  Attempting to fetch libgnome-keyring-3.10.1.tar.xz from http://www.mirrorservice.org/sites/ftp.gnome.org/pub/GNOME/sources/libgnome-keyring/3.10/
--->  Verifying checksums for libgnome-keyring
--->  Extracting libgnome-keyring
--->  Configuring libgnome-keyring
--->  Building libgnome-keyring

Been at this point for about three days now...

Update Building via sudo port -d install libgnome-keyring... full output at http://pastebin.com/WhE5zYhu but final part below (sits at this):

--->  Building libgnome-keyring
DEBUG: Executing org.macports.build (libgnome-keyring)
DEBUG: Environment: CPATH='/opt/local/include'      CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.9'
DEBUG: Assembled command: 'cd"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1" && /usr/bin/make -j4 -w all'
DEBUG: Executing command line:  cd"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1" && /usr/bin/make -j4 -w all 
make: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1'/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-recursive
make[1]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1'
Making all in .
make[2]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1'
Making all in egg
make[2]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg'
Making all in .
make[3]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg'
Making all in tests
make[3]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg/tests'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg/tests'
make[2]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/egg'
Making all in library
make[2]: Entering directory
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/library'
Making all in .
make[3]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_libgnome-keyring/libgnome-keyring/work/libgnome-keyring-3.10.1/library'

/bin/sh ../libtool  --tag=CC   --mode=link /usr/bin/clang  -Wall    -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes   -Wnested-externs -Wpointer-arith    -Wcast-align -Wsign-compare     -pipe -Os -arch x86_64 -g -Wno-strict-aliasing -Wno-sign-compare  -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -o libgnome-keyring-testable.la   gkr-callback.lo gkr-debug.lo gkr-misc.lo gkr-operation.lo gkr-session.lo gnome-keyring.lo gnome-keyring-memory.lo gnome-keyring-utils.lo ../egg/libegg.la -L/opt/local/lib -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl  -L/opt/local/lib -ldbus-1  -L/opt/local/lib -lgcrypt -lgpg-error -L/opt/local/lib -lgcrypt -lgpg-error 
libtool: link: rm -fr  .libs/libgnome-keyring-testable.lax
6
  • 1
    Could you run the command again but with the -d (debug) flag to show more output? – grg Feb 17 '14 at 17:42
  • I am using the restore_ports.tcl script (as per the upgrade instructions) and I don't know any TCL - can you tell me where to insert the flag in the script? – adrianmcmenamin Feb 18 '14 at 9:25
  • Use sudo port -d install libgnome-keyring to run just that portion with debugging on. – freiheit Feb 18 '14 at 19:18
  • Full output at pastebin.com/WhE5zYhu – adrianmcmenamin Feb 19 '14 at 10:00
  • The log looks OK = try a port clean libgnome-keyring and try again – mmmmmm Feb 21 '14 at 2:25
1
+50

Can you try:

sudo port uninstall libgnome-keyring
sudo port clean --all libgnome-keyring
sudo port selfupdate
sudo port -uc upgrade outdated
sudo port -d install libgnome-keyring

I just tried it myself and have considerably more output in my debug log. I'm wondering if your port tree is out of date maybe?

EDIT: I see your log has this line:

DEBUG: Skipping completed org.macports.configure (libgnome-keyring)

Which suggests the port hasn't been cleaned properly. Is that still showing up after doing the above?

Also I see this:

compiler clang 421.11.66 not blacklisted because it doesn't match {clang < 211.10.1}

What version of XCode are you running? Not 4.2 I hope? xcodebuild -version will tell you. You should be on 5.0.2. If you have to install or update from the App Store, you'll also want to run xcode-select --install to install the CLI tools.

7
  • Did you look at the full output in the pastebin? – adrianmcmenamin Feb 21 '14 at 8:06
  • Yup, mine (linked above) is 3 times as long. Though I don't see any errors in yours, clearly something is wrong. – miken32 Feb 21 '14 at 16:47
  • This is just the same - gets to build and then hits the processors hard but no sign that it will complete the build. – adrianmcmenamin Feb 21 '14 at 18:00
  • Any info from the XCode version check? – miken32 Feb 22 '14 at 6:09
  • Won't be near the box until Monday morning I'm afraid. – adrianmcmenamin Feb 22 '14 at 11:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .