Re: MacPorts selfupdate fails… v 1.9.2 to 2.0.3 w Xcode 4.1 - OSX 10.7.1

[Ryan Schmidt]

On Sep 12, 2011, at 14:54, William H. Magill wrote:

> ======================================================================
> # 27 inch iMac Intel (mid 2010) - 27 inch diagonal screen - Acquired 6/2011
> Model
> Processor 2.93 GHz Intel Core i7
> Memory  4 GB 1333 MHz DDR3
> Graphics  ATI Radeon HD 5750 1024 MB
> Display   27-inch (2560 x 1440)
> Software  Mac OS X Lion 10.7.1 (11B26)
> ======================================================================
> After failing to "selfupdate" under Xcode 4.0.2, I updated Xcode to 4.1 from the App Store, I got the same error as before (below), however the log file (below) as several different errors in it.
> 
> I also note that, other than what appear to be "normal" config failures, no errors are reported.
> 
> 
> outpost> sudo port selfupdate
> Password:
> --->  Updating the ports tree
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 1.9.2 installed,
> MacPorts base version 2.0.3 downloaded.
> --->  MacPorts base is outdated, installing new version 2.0.3
> Installing new MacPorts release in /opt/local as magill:admin; permissions 0755; Tcl-Package in /Library/Tcl
> 
> Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed (see log for details)
> [/opt/local] magill 
> 
> ----------------<cut here>---------------------------------
> outpost> ls -als  ./var/macports/sources/rsync.macports.org/release/base/config.log
> 60 -rw-r--r--  1 root  admin  58749 Sep 12 13:45 ./var/macports/sources/rsync.macports.org/release/base/config.log
> 
> outpost> more  ./var/macports/sources/rsync.macports.org/release/base/config.log
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.


[snip]

Right, the config.log only tells you about what happened during the configure phase, which appears to have completed just fine. Presumably an error is happening in a later phase, like the build phase. Re-run selfupdate with the verbose flag to see what's happening.

sudo port -v selfupdate