On Feb 16, 2015, at 12:01 PM, Brandon Allbery wrote: > On Mon, Feb 16, 2015 at 11:52 AM, YH Tan wrote: >> After you resolved the hostname, 'port selfupdate' was successful. But >> tesseract and ghostscript > > Erm, I didn't do anything. "hostname resolution" is the process of a client > looking up a hostname and converting it to a network address. I must conclude > that you had a temporary name service outage of some kind. > >>> Please see the log file for port xorg-libX11 for details: >>> >>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_xorg-libX11/xorg-libX11/main.log > > Without the contents of this logfile, nobody can even guess what the problem > is.
Looks like these are the two different xorg-libX11 configure failure tickets that were filed: https://trac.macports.org/ticket/46848 https://trac.macports.org/ticket/46877 Logs are attached there. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
