From owner-freebsd-ports Fri Dec 5 01:27:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA06150 for ports-outgoing; Fri, 5 Dec 1997 01:27:16 -0800 (PST) (envelope-from owner-freebsd-ports) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA06110; Fri, 5 Dec 1997 01:27:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA21878; Fri, 5 Dec 1997 01:27:07 -0800 (PST) To: Stefan Esser cc: ports@freebsd.org Subject: Re: Anyone build the latest KDE port under 2.2.5-stable lately? In-reply-to: Your message of "Fri, 05 Dec 1997 08:49:16 +0100." <19971205084916.47972@mi.uni-koeln.de> Date: Fri, 05 Dec 1997 01:27:07 -0800 Message-ID: <21874.881314027@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You must have lost the includes installed by the > kdelibs port ... > Rebuild and install that, and test again. I figured it out - the kdecore library was still in my ld cache even though I'd purged /usr/local/kde from the system (blah!) and it was false-detecting the kdelibs port as having been already built. This isn't the first time that ld cache poisoning has bit me before. You install a port, it ldconfigs the new libraries in, then you pkg_delete it and try doing another make - it sees the libs still in the ldconfig cache and your build falls over. Technically, of course, since the libraries were added by the install / pkg_add process they should be deleted by the pkg_delete. I suppose you could make this work fairly easily by hacking ``ldconfig -m'' to do a two-way merge: If you merge from a directory and there are entries in your cache which aren't still found there, they get deleted. Just add an `@unexec ldconfig -m %D' for each @exec ldconfig already there and you're in business. Hmmm. Sounds like work. :) Jordan