gnome failure, script failure

MrSmiley mrsmiley32 at gmail.com
Sun Feb 18 22:09:47 UTC 2007


amnesiac# ./gnomelogalyzer.sh

Generating build log. Please wait... done.

The cause of your build failure is not known to gnomelogalyzer.sh.  Before
e-mailing the build log to the FreeBSD GNOME team at freebsd-gnome at 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 at FreeBSD.org.  Archives can be
          searched at http://www.freebsd.org/gnome/index.html#search

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.

attached is the two log files needed, and as apparent the gnomelizer
didn't give anything useful, to double check I have the most current
ports, I did a cvs, that suceeded but portupgraded didn't go to well.

zsh: abort (core dumped)  pkgdb -F

at this point I'll take any advice you want to give but I may have to
suit without eclipse.


More information about the freebsd-gnome mailing list