Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
hello greg, thank you for your reply. > > i seem to recall a perl something or other flashing by on one of > > those root terminal screens. how does one preserve the > > information on those screensful? > man script > Use script to capture your entire upgrade process for analysis. Look > not only at the end where things totally crap out, but possibly much > earlier where things may start to fail in a non-fatal way (esp. if i'd forgotten the script trick. too far back in the memory banks i guess. > Sorry for not responding earlier... an unusual confluence of the > stars allowed me to take an actual vacation that involved no sounds like it must've been pretty good. > computers other than a GPS locator. Perhaps you've solved this by > now, but if not: i fed the file to the gnomelogalyzer script and it basically told me that it couldn't help. (!) subsequently, i've seen messages suggesting that all i needed was linuxpluginwrapper and one other port (the name of which eludes me at the moment) installed. i've made sure they're installed, but as it turns out, i haven't needed the plugins at any of the sites i've visited. regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
David Armour wrote: i seem to recall a perl something or other flashing by on one of those root terminal screens. how does one preserve the information on those screensful? Sorry for not responding earlier... an unusual confluence of the stars allowed me to take an actual vacation that involved no computers other than a GPS locator. Perhaps you've solved this by now, but if not: man script Use script to capture your entire upgrade process for analysis. Look not only at the end where things totally crap out, but possibly much earlier where things may start to fail in a non-fatal way (esp. if you are portupgrading a glob of things, or -a, rather than focusing on individual packages). -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
hello greg, thanks for your response. > In a couple of cases where I had issues like this with gnome > installation (and the XML-Parser thing sounds awfully > familiar), I think I found that it was most efficient to do the gnome faq, as well as the information that the gnomelogalyzer puts out, seems to suggest portupgrading -a as a front line of defence. sadly, this approach seems to conflict with the /usr/ports/UPDATING, esp. wrt KDE, at least as far as i understand it. YMMV, & YMNEGTCS... (you may not even get the car started.) etc., etc. > gnome very much depends on other things being up to date > though. Modify to suit your port management habits. well, yes. in a moment of hubris, i went ahead and portupgraded the cups-base port, thinking that a long time ago, in a galaxy far far away, i was also looking to get a second-hand laserprinter working with cups [up-music: theme from jaws?] > Note that my recipe will have you using perl5.8 during the > gnome upgrade. The tip on using 5.6.2 instead might be another i seem to recall a perl something or other flashing by on one of those root terminal screens. how does one preserve the information on those screensful? it's clunking away on something to do with koffice at the moment. -- = df(dave)armourmyrealboxcalm! = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
On Thursday 22 September 2005 22:18, Peter Clutton wrote: > On 9/22/05, David Armour <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED], 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 [EMAIL PROTECTED] 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! = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
Peter Clutton wrote: On 9/23/05, Gregory Nou <[EMAIL PROTECTED]> wrote: You should install port textproc/p5-XML-Parser, and if already installed, verify that the link are well done in your /usr/local/bin (eg : not something like using perl5.8 and having perl pointing on perl5.6.2) Thanks for that. I usually check out the port it mentions in it's output, but the XML-parser thing threw me. Will have a look tonight and let you know. In a couple of cases where I had issues like this with gnome installation (and the XML-Parser thing sounds awfully familiar), I think I found that it was most efficient to do something like: portupgrade [args] perl perl-after-upgrade portupgrade Then the gnome install would run just swell. This was several months ago, so my memory could be a bit fuzzy on this. I think the gnome FAQ indicates one should just "portupgrade -a" first, but of course that doesn't always work out well since -a includes gnome if already installed. Success with gnome very much depends on other things being up to date though. Modify to suit your port management habits. Note that my recipe will have you using perl5.8 during the gnome upgrade. The tip on using 5.6.2 instead might be another way around, but I'm pretty sure the root of the problems I had were actually with imake and maybe other X stuff not being in the state required, even though the evident choke symptom is on a perl module. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
On 9/23/05, Gregory Nou <[EMAIL PROTECTED]> wrote: > > You should install port textproc/p5-XML-Parser, and if already > installed, verify that the link are well done in your /usr/local/bin (eg > : not something like using perl5.8 and having perl pointing on perl5.6.2) Thanks for that. I usually check out the port it mentions in it's output, but the XML-parser thing threw me. Will have a look tonight and let you know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
Peter Clutton wrote: On 9/22/05, David Armour <[EMAIL PROTECTED]> wrote: i was trying to install the plugger-plugins-hubbe port as a way to get plugins to work with firefox. . . checking whether gmake sets $(MAKE)... yes checking for intltool >= 0.30... 0.33 found checking for perl... /usr/bin/perl checking for XML::Parser... ===> Script "configure" failed unexpectedly. i have the directed output file (make_failure_file), gnomelogalyzer.sh, and pages of non-helpful googled info. where would i find out how to feed a file to a script? thanks in advance, both for your patience, and for any info. When you've run it, would you let us know the outcome? I had *exactly* the same error messages multiple times trying to installing gnome, stuff bout XML Parser script configure failed unexpextedly. I haven't had a chance to feed it to gnomealyzer, but will post if i get something good from it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Seems that it's not a gnome related problem. You should install port textproc/p5-XML-Parser, and if already installed, verify that the link are well done in your /usr/local/bin (eg : not something like using perl5.8 and having perl pointing on perl5.6.2) Cheers -- Grégory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
On 9/22/05, David Armour <[EMAIL PROTECTED]> wrote: > > > i was trying to install the plugger-plugins-hubbe port as a way to get > plugins to work with firefox. . . > > checking whether gmake sets $(MAKE)... yes > checking for intltool >= 0.30... 0.33 found > checking for perl... /usr/bin/perl > checking for XML::Parser... ===> Script "configure" failed > unexpectedly. > > i have the directed output file (make_failure_file), gnomelogalyzer.sh, > and pages of non-helpful googled info. where would i find out how to > feed a file to a script? > > thanks in advance, both for your patience, and for any info. > > When you've run it, would you let us know the outcome? I had *exactly* the same error messages multiple times trying to installing gnome, stuff bout XML Parser script configure failed unexpextedly. I haven't had a chance to feed it to gnomealyzer, but will post if i get something good from it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
Benjamin Braatz wrote: Am 22.09.2005 um 17:49 schrieb David Armour: ... to presume further on your kindness, a follow-up question: i believe i have bash installed. should i replace "/bin/sh" above with "/bin/bash" or does it make any difference? Probably it wouldn't make too much of a difference, but the script was, if I see this correctly, designed to work with the Bourne shell (/bin/ sh) delivered with FreeBSD (i.e. installed in any case). Yes, if the script is portable, sticking with /bin/sh is entirely reasonable, and ought to work just fine with Linux systems who have Bash as their /bin/sh. BTW, your installed bash is third-party software from FreeBSDs point of view (installed via ports or packages), and will hence be found in /usr/local/bin/bash, not in /bin/bash. It's reasonable to make a symlink from /bin/bash to /usr/local/bin/bash, just so long as nothing tries to use Bash before /usr is mounted when the system starts up... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
Hello, Am 22.09.2005 um 17:49 schrieb David Armour: ... to presume further on your kindness, a follow-up question: i believe i have bash installed. should i replace "/bin/sh" above with "/bin/bash" or does it make any difference? Probably it wouldn't make too much of a difference, but the script was, if I see this correctly, designed to work with the Bourne shell (/bin/ sh) delivered with FreeBSD (i.e. installed in any case). BTW, your installed bash is third-party software from FreeBSDs point of view (installed via ports or packages), and will hence be found in /usr/local/bin/bash, not in /bin/bash. Greetings -- Benjamin Braatz [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
hello, thank you for your reply. > > i have the directed output file (make_failure_file), > > gnomelogalyzer.sh, > > /bin/sh gnomelogalyzer.sh < make_failure_file [checking my head for glasses, before asking "where are my glasses?"] ... to presume further on your kindness, a follow-up question: i believe i have bash installed. should i replace "/bin/sh" above with "/bin/bash" or does it make any difference? [trying not to break anything...] regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
David Armour <[EMAIL PROTECTED]> writes: > hello list! > > i was trying to install the plugger-plugins-hubbe port as a way to get > plugins to work with firefox. . . > > ===> Configuring for libgda2-1.2.2_1 > checking for a BSD-compatible install... /usr/bin/install -c -o root -g > wheel > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... no > checking for nawk... nawk > checking whether gmake sets $(MAKE)... yes > checking for intltool >= 0.30... 0.33 found > checking for perl... /usr/bin/perl > checking for XML::Parser... ===> Script "configure" failed > unexpectedly. > Please direct the output of the failure of the make command to a file, > and then feed that file to the gnomelogalyzer, available from > http://www.freebsd.org/gnome/gnomelogalyzer.sh, which will diagnose the > problem and suggest a solution. If - and only if - the gnomelogalyzer > cannot solve the problem, report the problem to the FreeBSD GNOME team > at [EMAIL PROTECTED], and attach "/usr/ports/databases/ \ > libgda2/work/libgda-1.2.2/config.log" and the output of the failure of > the make command. Also, it might be a good idea to provide an overview > of all packages installed on your system (e.g. an `ls /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/databases/libgda2. > *** Error code 1 > > Stop in /usr/ports/math/gnumeric. > *** Error code 1 > > Stop in /usr/ports/www/plugger-plugins-hubbe. > > i have the directed output file (make_failure_file), gnomelogalyzer.sh, > and pages of non-helpful googled info. where would i find out how to > feed a file to a script? /bin/sh gnomelogalyzer.sh < make_failure_file ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NEWBIE: how-to for feeding file to gnomealyzer.sh?
hello list! i was trying to install the plugger-plugins-hubbe port as a way to get plugins to work with firefox. . . ===> Configuring for libgda2-1.2.2_1 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether gmake sets $(MAKE)... yes checking for intltool >= 0.30... 0.33 found checking for perl... /usr/bin/perl checking for XML::Parser... ===> Script "configure" failed unexpectedly. Please direct the output of the failure of the make command to a file, and then feed that file to the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the problem to the FreeBSD GNOME team at [EMAIL PROTECTED], and attach "/usr/ports/databases/ \ libgda2/work/libgda-1.2.2/config.log" and the output of the failure of the make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/databases/libgda2. *** Error code 1 Stop in /usr/ports/math/gnumeric. *** Error code 1 Stop in /usr/ports/www/plugger-plugins-hubbe. i have the directed output file (make_failure_file), gnomelogalyzer.sh, and pages of non-helpful googled info. where would i find out how to feed a file to a script? thanks in advance, both for your patience, and for any info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
