Re: FYI - MacPorts selfupdate fails… v 1.9.2 to 2.0.3 .. no log file produced (in an obvious place) w Xcode 4.0.2 - OSX 10.7.1

[Ryan Schmidt]

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

> Note: this particular error happened before I realized I did not upgrade Xcode on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed again after updating to Xcode 4.1.)
> This posting is simply "for the record" -- that the message needs to be expanded :).

"the message": you mean the message "see log for details"? That's a generic error printed any time any shell command files, so it can't be more specific. We could print an additional message with the log location; we do that for port installs already.


> outpost> sudo port selfupdate
> Password:
> Warning: port definitions are more than two weeks old, consider using selfupdate
> --->  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)
> 
> ….. Could not find any log …. in  /opt/local or in /var/log or /library/logs
> 
> Finally found: 
>        /opt/local/var/macports/sources/rsync.macports.org/release/base/config.log
> 
> I guess that is the log being talked about as there are no others in /opt/local according to "find"… however it doesn't say anything other than to look for the errors in the ?same? file.

I don't think that's the log we're talking about, but I don't know where a selfupdate log would be. We may not have one. As I said the "see log" message is generic, and usually occurs during port installs, where we do have a log.

You've already found that not upgrading your Xcode was the problem, but if you were still searching for the cause of the problem, I would have advised you to re-run with the verbose flag, to get more output.

sudo port -v selfupdate


I'm actually surprised that our MacPorts configure script doesn't check for incompatible Xcode versions. All we check is:

case "$XCODE_VERSION" in
  1.*|2.[[0-1]]*)
    AC_MSG_WARN([This version of Xcode Tools is not supported])
    AC_MSG_WARN([Please upgrade at http://connect.apple.com/])
    ;;
  2.[[2-3]]*|3.[[0]]*)
    AC_MSG_WARN([This version of Xcode Tools is out of date])
    AC_MSG_WARN([Please consider upgrading as some ports fail compiling])
    ;;
  2.*|3.*|4.*)
    dnl Supported version
    ;;
  *)
    ;;
esac

That's fine as far as it goes, but I thought we were already checking for Xcode/OS version mismatches; I guess we're not.



> [Annoying … the Appstore  download of the lion Xcode4 update … doesn't do anything. You have to launch the installer manually.]

That's correct. The people to complain to about that are Apple, not us.