On 4/22/13, Clemens Lang <[email protected]> wrote: > On Mon, Apr 22, 2013 at 07:48:54AM -0600, Roger Pack wrote: >> Suggestion/feature request: similarly have a log file (and tell where >> it is) for this failure, as, currently, it doesn't tell me information >> about *which* command failed, and how, etc. > > While I agree this would be helpful, you can run with -d to get the > output needed to debug this.
Yes, I was just saying that in the "typical" case, it doesn't give you a hint as to how to get the output needed, whereas installing a package does (it would help out this novice user, at least, I basically had to ask on the ML, as you can see). Thanks! -roger- _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
