On May 24, 2010, at 06:00, MacPorts wrote:
> +== MacPorts Installation Order ==#macportsinstall
> +
> +'''Error message:'''[[BR]]
> +{{{
> +Error: Unable to execute port: upgrade gettext failed
> +}}}
This is a pretty generic error message which would occur anytime gettext cannot
be upgraded for any reason. Perhaps you should be more specific about the
problem you're encountering. For example, I have a feeling these tickets are
the same issue with respect to the zlib port:
http://trac.macports.org/ticket/24599
http://trac.macports.org/ticket/24896#comment:2
(I still need to test whether that's true.)
With MacPorts 1.9+, MacPorts will check for Xcode and warn if it's not
installed.
http://trac.macports.org/ticket/12794
However, that doesn't solve the problem that if you try to install a port, it
fails because Xcode isn't there, you then install Xcode, and then continue
trying to install the port, without cleaning it first, it may fail with
fascinating error messages.
> +'''Workaround:'''[[BR]]
> +
> +You may of installed MacPorts before installing Xcode tools. In which case,
> uninstall MacPorts with the guide
> [http://guide.macports.org/chunked/installing.macports.uninstalling.html] and
> then re-install.
You hardly need to uninstall and reinstall MacPorts to correct this problem.
You just need to clean the port that's failing to build (e.g. "sudo port clean
gettext").
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
