It's true that we don't have SUNWGlib on our build machines, but the build should not fail even if you have it there. It would be nice to get to the bottom of this and find out why and how libglib.so was picked up.
If you can upload a Makefile, config.log and config.status that might help. Thanks, Laca On Fri, 2008-01-11 at 22:25 +0100, Patrick Ale wrote: > On Jan 11, 2008 9:13 PM, Damien Carbery <Damien.Carbery at sun.com> wrote: > >> I searched my rarian build directory for 'lglib' but did not find > any occurances. > > Probably because I am an idiot and you people didn't install SUNWGlib > from the sfwnv-gate ... I did... :s > I really should keep a log about what I install... > > $ pkginfo -l SUNWGlib > PKGINST: SUNWGlib > NAME: GLIB - Library of useful routines for C programming > CATEGORY: system > ARCH: i386 > VERSION: 11.11.0,REV=2007.11.16.16.36 > BASEDIR: / > VENDOR: Sun Microsystems, Inc. > DESC: GLIB - Library of useful routines for C programming > PSTAMP: sfwnv-x20071116164939 > INSTDATE: Jan 01 2008 14:16 > HOTLINE: Please contact your local service provider > STATUS: completely installed > FILES: 27 installed pathnames > 7 shared pathnames > 9 directories > 7 executables > 451 blocks used (approx)
