Re: pkg/44590: x11/kdebase3 attempts to link against non-existant library (NetBSD 5.0 / i386)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/44590; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/44590: x11/kdebase3 attempts to link against non-existant 
library (NetBSD 5.0 / i386)
Date: Fri, 18 Feb 2011 19:13:23 +0700

     Date:        Fri, 18 Feb 2011 08:20:04 +0000 (UTC)
     From:        Thomas Klausner <wiz%NetBSD.org@localhost>
     Message-ID:  <20110218082004.D683A63B100%www.NetBSD.org@localhost>
 
   |  The bulk builds clean up after themselves, so I don't think it's a
   |  general problem.
 
 I thought they did too, but I wasn't sure what they build as a single
 object (if it was just meta-packages/kde3 then it wouldn't see it, but
 as I don't use it, I have no idea what's up.
 
   |  I'm guessing this is some local problem (how do you set your WRKDIR,
   |  for example?) but I don't understand it :)
 
 It's set by the pkg_comp configuration, which puts in (the sandbox version
 of) /etc/mk.conf ...
 
 MKOBJDIRS ?= yes
 WRKDIR_BASENAME ?= 5
 WRKOBJDIR ?= /pkg_comp/obj/pkgsrc
 
 The '5' is just what I use when I'm building NetBSD 5.0 packages
 (it would be "4x" for NetBSD 4 with modular xorg) - it's just a
 short meaningless string.)   /pkg_comp/obj/pkgsrc is pkg_comp's
 default home for work dirs (since it is in the sandbox, I can't
 think of any reason anyone would ever need to alter it).
 
 But this stuff hasn't altered  in years, and kdebase3 built just fine
 last July in the same build environment.
 
 I was actually wondering if there might have been some bug somewhere
 in the build system that might have caused my binary package of kdelibs3
 (or perhaps libart or arts or something) to have been built incorrectly -
 any libtool or buildlink bugs added and fixed sometime around a month ago
 that anyone remembers (I haven't been following the lists closely during
 this period - it is the busy time of the year for me - end of the academic
 year.)
 
 If that's what it was, then just rebuilding kdelibs3 (or whatever) would fix
 things for me, but I'd like to either understand, or at least know that
 someone else understands, the cause of the problem before I resort to black
 magic or voodoo type fix attempts.
 
 I'm going to see if I can find where these bogus paths originate, to see
 what that comes from, but that may end up taking some time to accomplish.
 
 kre