From owner-freebsd-questions@FreeBSD.ORG Sat Sep 24 04:27:09 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC97916A41F for ; Sat, 24 Sep 2005 04:27:09 +0000 (GMT) (envelope-from dfarmour@myrealbox.com) Received: from pd4mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5632643D49 for ; Sat, 24 Sep 2005 04:27:09 +0000 (GMT) (envelope-from dfarmour@myrealbox.com) Received: from pd4mr6so.prod.shaw.ca (pd4mr6so-qfe3.prod.shaw.ca [10.0.141.69]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0INB00LVH0ALNE30@l-daemon> for freebsd-questions@freebsd.org; Fri, 23 Sep 2005 22:25:33 -0600 (MDT) Received: from pn2ml1so.prod.shaw.ca ([10.0.121.145]) by pd4mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0INB00D2D0ALIJA0@pd4mr6so.prod.shaw.ca> for freebsd-questions@freebsd.org; Fri, 23 Sep 2005 22:25:33 -0600 (MDT) Received: from s0106000d87ae2db6.gv.shawcable.net (S0106000d87ae2db6.gv.shawcable.net [24.108.158.228]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0INB00MC60AK35@l-daemon> for freebsd-questions@freebsd.org; Fri, 23 Sep 2005 22:25:33 -0600 (MDT) Date: Fri, 23 Sep 2005 21:26:35 -0700 From: David Armour In-reply-to: <57416b300509222218697a524b@mail.gmail.com> To: Peter Clutton , freebsd-questions@freebsd.org Message-id: <200509232126.36670.dfarmour@myrealbox.com> Organization: dfa@no_spam.net MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200509212203.35549.dfarmour@myrealbox.com> <57416b300509222218697a524b@mail.gmail.com> User-Agent: KMail/1.8.2 Cc: Subject: Re: NEWBIE: how-to for feeding file to gnomealyzer.sh? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Sep 2005 04:27:09 -0000 On Thursday 22 September 2005 22:18, Peter Clutton wrote: > On 9/22/05, David Armour wrote: > > i was trying to install the plugger-plugins-hubbe port as a > > i have the directed output file (make_failure_file), > > gnomelogalyzer.sh, and pages of non-helpful googled info. > > When you've run it, would you let us know the outcome? I had > same error messages multiple times trying to installing gnome, > stuff bout XML Parser script configure failed unexpextedly. I thanks for your response. here's the result when i ran the logalyzer script: =================== Generating build log. Please wait... done. The cause of your build failure is not known to nomelogalyzer.sh. Before e-mailing the build log to the FreeBSD GNOME team at freebsd-gnome@FreeBSD.org, TRY EACH OF THE FOLLOWING: * If you are generating your own logfile, make sure to generate it with something similar to: "make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or "make |& tee /path/to/logfile" (csh/tcsh) * Make sure your cvsup(1) configuration file specifies the 'ports-all' collection * Run cvsup(1) and attempt the build again * Check /usr/ports/UPDATING for information pertinent to your build failure * 99% of the commonly reported build failures can be solved by running "portupgrade -a" * Read the FAQs at http://www.FreeBSD.org/gnome/ * Search the archives of freebsd-gnome@FreeBSD.org. Archives can be searched at http://lists.freebsd.org/pipermail/freebsd-gnome/ If you have not performed each of the above suggestions, don't bother asking for help. The chances are good that you'll simply be told to perform one of the aforementioned steps. ========================================= the key phrase here -- The cause of your build failure is not known to nomelogalyzer.sh. -- prompted me to run down the list looking for something/anything that i a) understood, and b) could implement. the first thing that met these criteria was running cvsup again, and i'm midst of running portupgrade on a cups-base port at the moment. i'm not sure that that was such a wise decision since the box has been chunking away now for several hours. hope this helps. i *have* successfully upgraded an xterm, opera, and firefox port before my own native hubris perhaps unwisely convinced me to attempt the cups-base upgrade. but as far as getting around to the plugger-plugins-hubbe port upgrade which was the nominal reason for getting into this in the first place, well, the jury's still out, at this point. -- = df(dave)armourmyrealboxcalm! =