Port net-im/empathy/ possible broken
Jeremy Messenger
mezz.freebsd at gmail.com
Wed Jun 29 18:59:38 UTC 2011
On Sun, Jun 26, 2011 at 6:06 PM, Aleksey Spiridonov <leksey at ya.ru> wrote:
> Hello.
>
> Same bug finds at
> http://lists.pcbsd.org/pipermail/pbibuild/2011-June/034842.html
>
> My config.log in attach
The pointyhat[1] and I can't reproduce it. You will need to make sure
to follow this: http://www.freebsd.org/gnome/docs/bugging.html
[1] http://pointyhat.freebsd.org/errorlogs/amd64-8-latest-logs/empathy-2.32.2_1.log
Cheers,
Mezz
> # ./gnomelogalyzer.sh output
>
> 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.
--
mezz.freebsd at gmail.com - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org
More information about the freebsd-gnome
mailing list