From owner-freebsd-gnome@FreeBSD.ORG Tue Aug 1 17:11:44 2006 Return-Path: X-Original-To: gnome@freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18AA816A4DA for ; Tue, 1 Aug 2006 17:11:44 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from centrmmtao02.cox.net (centrmmtao02.cox.net [70.168.83.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E2943D49 for ; Tue, 1 Aug 2006 17:11:43 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([24.255.149.218]) by centrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060801171142.NQTY22014.centrmmtao02.cox.net@mezz.mezzweb.com>; Tue, 1 Aug 2006 13:11:42 -0400 Date: Tue, 01 Aug 2006 12:11:53 -0500 To: "..:: Cleber ::.." From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: User-Agent: Opera Mail/9.00 (Linux) Cc: gnome@freebsd.org Subject: Re: Problem with installation of the gconf2 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 17:11:44 -0000 On Tue, 01 Aug 2006 08:55:34 -0500, ..:: Cleber ::.. = 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 >=3D 2.7.0 gobject-2.0 >=3D 2.7.0 ORBit-2.0 >=3D 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. > > =3D=3D=3D> 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@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 sys= tem > (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 li= st > (gnome@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@FreeBSD.org, > TRY EACH OF THE FOLLOWING: > > * If you are generating your own logfile, make sure to generate it w= ith > 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. > ----------------------------------------------------------------------= ------------------------------------ -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org