Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Aug 2002 20:10:30 +0200 (CEST)
From:      la hache <lah@pandora.be>
To:        Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        gnome@FreeBSD.ORG
Subject:   Re: CAN compile atk
Message-ID:  <20020813201015.D332-100000@archipelagos.pandora.be>
In-Reply-To: <1029260842.311.17.camel@gyros.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
hum. and on which faq should i have been supposed to know about this ?


On 13 Aug 2002, Joe Marcus Clarke wrote:

> On Tue, 2002-08-13 at 13:42, la hache wrote:
> > OMG. i pkg_deleted pkg-config, and made install it from ports. and now it
> > works !! this is wonderful. thanks so much. i have bumped som any tims on
> > this stupid broken branch in my system (cvsupped again and again from
> > 4.4). it also explains why i never had the problem on newer systems. but
> > it doesn't explain why i kept having 0.12.0 when doing pkg-config
> > --version. i don't understand " Did you build 0.12.0 directly from the
> > distfile?  If so, it's broken. ". can you please explain ?
>
> I wrote a patch for pkgconfig so that it worked properly under 4.x.  I
> sent the patch to the author, but he never integrated it.  Therefore,
> the only working pkgconfig for FreeBSD 4.x is the one in the ports
> collection.
>
> Joe
>
> >
> >
> > On 13 Aug 2002, Joe Marcus Clarke wrote:
> >
> > > On Tue, 2002-08-13 at 13:06, la hache wrote:
> > > > my pkg-config has been version 0.12.0 for ages, the .pc file is in the
> > > > right location and contains the exact same string that you gave me. i
> > > > really don't understand. on all my secondary freebsd systems where i
> > > > installed 4.6 from scratch on then cvsupped (even from 4.5), atk compiled
> > > > like a breeze. something must be broken on this system, but what ?
> > >
> > > If this is the case, why does your pkg_info output list pkgconfig as
> > > 0.8.0?  Did you build 0.12.0 directly from the distfile?  If so, it's
> > > broken.  You can see exactly what pkg-config produces for glib by doing:
> > >
> > > pkg-config --cflags glib-2.0
> > >
> > > If this is an isolated incident, you might also consider rebuilding this
> > > machine.
> > >
> > > Joe
> > >
> > > >
> > > >
> > > > On 13 Aug 2002, Joe Marcus Clarke wrote:
> > > >
> > > > > On Tue, 2002-08-13 at 09:48, la hache wrote:
> > > > > > i can't compile atk with latest cvs tree:
> > > > > >
> > > > > > checking for GLIB - version >= 2.0.0... no
> > > > > > *** Could not run GLIB test program, checking why...
> > > > > > *** The test program failed to compile or link. See the file config.log
> > > > > > for the
> > > > > > *** exact error that occured. This usually means GLIB is incorrectly
> > > > > > installed.
> > > > > > configure: error:
> > > > > >
> > > > > > but glib 2.0.6 is installed ! i don't understand.
> > > > >
> > > > > Here's the thing.  GNOME configure scripts are using the pkgconfig
> > > > > package (which installs the /usr/local/bin/pkg-config binary) to read
> > > > > the .pc files to determine package properties for the various
> > > > > dependencies.
> > > > >
> > > > > Around line 7290, configure uses /usr/local/bin/pkg-config to try and
> > > > > detect glib.  In order to do this, you need a
> > > > > /usr/local/libdata/pkgconfig/glib-2.0.pc file.  This file should contain
> > > > > the following for Cflags:
> > > > >
> > > > > -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include
> > > > >
> > > > > One of three things aren't happening.  Either glib-2.0.pc exists in the
> > > > > right path, but pkg-config isn't looking there, or the file doesn't
> > > > > exist,  or the Cflags are incorrect.  As you can see from line 7471,
> > > > > configure is compiling the glib test program _without_ the correct
> > > > > include path.  Therefore, it doesn't find glib.h, and the test program
> > > > > doesn't build.
> > > > >
> > > > > So, once you've checked to make sure the glib-2.0.pc exists in the right
> > > > > location, then upgrade pkgconfig _from ports_ to 0.12.0 (mandatory for
> > > > > FreeBSD 4.x).  Then, verify the contents of the glib-2.0.pc file are
> > > > > good.  After that, I see no reason why GNOME 2.0 (or at least atk)
> > > > > shouldn't build for you.
> > > >
> > > >
> > > --
> > > PGP Key : http://www.marcuscom.com/pgp.asc
> > >
> > >
> > >
> >
> >
> --
> PGP Key : http://www.marcuscom.com/pgp.asc
>
>
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-gnome" in the body of the message




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