Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Feb 2011 21:23:57 +0100
From:      Koop Mast <kwm@rainbow-runner.nl>
To:        "Marcelo C. Mota" <marcelo.mota@cpaa.embrapa.br>
Cc:        gnome@freebsd.org
Subject:   Re: gnomelogalyzer cannot solve the problem
Message-ID:  <1298319837.45274.1.camel@crashalot.rainbow-runner.nl>
In-Reply-To: <20ee46036430a0bf3a3d0fcc014b694d.squirrel@www2.cpaa.embrapa.br>
References:  <20ee46036430a0bf3a3d0fcc014b694d.squirrel@www2.cpaa.embrapa.br>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2011-02-21 at 15:25 -0400, Marcelo C. Mota wrote:
> *** Error code 1
> 
> Stop in /usr/ports/devel/gobject-introspection.
> *** Error code 1

You didn't fail to include the actual error. Can you include it? And I
agree that the analiser script needs to be updated, to these new
failures.

-Koop

> Stop in /usr/ports/multimedia/gstreamer.
> *** Error code 1
> 
> Stop in /usr/ports/multimedia/gstreamer-plugins.
> *** Error code 1
> 
> Stop in /usr/ports/x11-toolkits/wxgtk28-unicode.
> *** Error code 1
> 
> Stop in /usr/ports/x11-toolkits/wxgtk28-unicode.
> *** Error code 1
> 
> Stop in /usr/ports/lang/erlang.
> *** Error code 1
> 
> Stop in /usr/ports/lang/erlang.
> *** Error code 1
> 
> Stop in /usr/ports/net-im/ejabberd.
> *** Error code 1
> 
> Stop in /usr/ports/net-im/ejabberd.
> 
> GNOMELOGALYZER
> candiru# sh 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@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://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.
> 
> 
> _______________________________________________
> freebsd-gnome@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1298319837.45274.1.camel>