From owner-freebsd-ports  Wed Jun 16 18:37: 7 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from poseidon.student.umd.edu (ppp-27-192.tidalwave.net [208.220.27.192])
	by hub.freebsd.org (Postfix) with ESMTP id 942321507B
	for <freebsd-ports@FreeBSD.ORG>; Wed, 16 Jun 1999 18:36:52 -0700 (PDT)
	(envelope-from bfoz@glue.umd.edu)
Received: from glue.umd.edu (localhost [127.0.0.1])
	by poseidon.student.umd.edu (8.9.3/8.9.3) with ESMTP id VAA00526;
	Wed, 16 Jun 1999 21:35:07 -0400 (EDT)
	(envelope-from bfoz@glue.umd.edu)
Message-ID: <37683694.462D61AD@glue.umd.edu>
Date: Wed, 16 Jun 1999 19:43:16 -0400
From: Brandon Fosdick <bfoz@glue.umd.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeremy Lea <reg@shale.csir.co.za>
Cc: freebsd-ports@FreeBSD.ORG
Subject: Re: Help! gtk, glib, imlib library names wrong?
References: <37611753.1D2B5FA9@glue.umd.edu> <19990612132526.A71883@shale.csir.co.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Jeremy Lea wrote:
> 
> Hi,
> 
> On Fri, Jun 11, 1999 at 10:04:03AM -0400, Brandon Fosdick wrote:
> > I just cvsup'd the latest ports and went to install gnome, etc...
> > imlib's makefile looks for gtklib12 but gtk12 installed gtklib-12 so 'make
> > install' thinks gtk isn't installed (but it is). Temp fix: changed imlib's
> > makefile. But... 'make configure', while testing for gtk, compiles a test
> > program which links to gtklib12. 'ldconfig -r' doesn't know anything about
> > gtklib12, but it does have gtklib-12. Temp fix: add '--disable-gtktest' to
> > CONFIG_ARGS in makefile. However, when it comes time to build, nothing can
> > link to gtk since ld is looking for gtklib12, which isn't there. Similar
> > story with glib during install of gtk.
> >
> > None of this happened last time i installed these ports. I've already tried
> > linking gtklib12 to gtklib-12.so.2 and then running ldconfig. Didn't work. Any
> > ideas?
> 
> Uninstall these ports and the libtool port, then reinstall them.  This
> is caused by an out of date libtool.  Unfortunately, the changes to
> bsd.port.mk which check for this haven't made it in yet.

That fixed it. Thanks. 

-Brandon




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