David T. wrote: [] > I know that I am probably not providing the information you all need, but the > output goes on forever, and I honestly wouldn't know which of the miles of > output held the clue to inner salvation...
Here is a short recipe: 1. Try to identify the *first* error message in the output. It can be indicated by the word "error", but this isn't necessarily so. It depends of who is talking. If it's the compiler, then any message that is not marked as "warning" is an error message. 2. Show everything from the beginning of the last command that was executed before the error, up to the error. 3. Show the end of the output with the package name and version. And don't forget your fink version and OSX version. -- Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
