Problem with installation of the gconf2

[Jeremy Messenger]

On Tue, 01 Aug 2006 08:55:34 -0500, ..:: Cleber ::..  
<clebermartim at gmail.com> wrote:

> (b) the output of the failed make command
>
> ...
> checking for pkg-config... /usr/local/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for DEPENDENT... configure: error: Package requirements  
> (glib-2.0 > 2.9
> .0 gmodule-2.0 >= 2.7.0 gobject-2.0 >= 2.7.0 ORBit-2.0 >= 2.4.0) were  
> not met:
>
> Requested 'glib-2.0 > 2.9.0' but version of GLib is 2.8.6

Here has said it all as we have glib-2.10.3 and you have glib-2.8.6_1.  
Please visit http://www.freebsd.org/gnome/docs/bugging.html and be sure to  
follow the '1. When should I make a bug report?'.

Cheers,
Mezz

> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables DEPENDENT_CFLAGS
> and DEPENDENT_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> ===>  Script "configure" failed unexpectedly.
> Please run 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 build failure to the FreeBSD GNOME team at
> gnome at FreeBSD.org, and attach (a)
> "/usr/ports/devel/gconf2/work/GConf-2.14.0/config.log", (b) the output  
> of the
> failed make command, and (c) the gnomelogalyzer output. Also, it might  
> be a
> good idea to provide an overview of all packages installed on your system
> (i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
> copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1)  
> with
> the attachment. Try to avoid sending any attachments to the mailing list
> (gnome at FreeBSD.org), because attachments sent to FreeBSD mailing lists  
> are
> usually discarded by the mailing list software.
> *** Error code 1
>
> Stop in /usr/ports/devel/gconf2.
> ----------------------------------------------------------------------------------------------------------
>
> (c) the gnomelogalyzer 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.
> ----------------------------------------------------------------------------------------------------------



-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia at FreeBSD.org