pkg/34972: www/nvu fails to configure (libIDL config script not found)

[kre%munnari.OZ.AU@localhost]

>Number:         34972
>Category:       pkg
>Synopsis:       www/nvu fails to configure (libIDL config script not found)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 02 12:55:00 +0000 2006
>Originator:     Robert Elz
>Release:        NetBSD 3.99.15   (pkgsrc current today)
>Organization:
        Prince of Songkla University
>Environment:
System: NetBSD jade.coe.psu.ac.th 3.99.15 NetBSD 3.99.15 
(GENERIC-1.696-20060125) #8: Wed Jan 25 04:59:39 ICT 2006 
kre%jade.coe.psu.ac.th@localhost:/usr/obj/current/kernels/JADE_ASUS i386
Architecture: i386
Machine: i386
>Description:
        www/nvu seems to be unable to find libIDL's config script.

>How-To-Repeat:
        I use pkg_comp w9th libkver and NetBSD-3.0 sets installed and
        bse the bin-install target to build (and install from) binary
        packages.  Tyhe sandbos has

libIDL-0.8.7        CORBA Interface Definition Language parser

        istalled in it.   "pkg_comp build www/nwu" generates ...

checking for GLIB - version >= 1.2.0... yes
checking for libIDL-config... no
checking for libIDL - version >= 0.6.3... no
*** The libIDL-config script installed by libIDL could not be found
*** If libIDL was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the LIBIDL_CONFIG environment variable to the
*** full path to libIDL-config.
checking for orbit-config... no
configure: error: libIDL not found.
        libIDL 0.6.3 or higher is required.
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/www/nvu
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/www/nvu
*** Error code 1

Stop.

        PREFIX/bin (assuming PREFIX means /usr/pkg which is where
        I install things (ie: the default place) is certainly in *my*
        path, and that carries through to root's path (I use "su -m")
        for root to use pkg_comp - but whether it remains in $PATH
        for a "pkg_comp build" I have no idea.   Package building
        Should neevr care what is in $PATH in any event though (that
        would just lead to inconsistent results).

>Fix:
        ???