On Jul 25, 2006, at 7:37 AM, Todd Vierling wrote:

> On 7/25/06, Joerg Sonnenberger <joerg@britannica.bec.de> wrote:
>> > When installing a package, pkgsrc sets LIBTOOL to "libtool" instead
>> > of its full path, even though 'make show-var VARNAME=LIBTOOL' shows
>> > the full path.  Because of this, "make install" fails if the root
>> > user does not have "libtool" available in its path (For example,
>> > graphics/MesaLib calls ${LIBTOOL} to install libraries at pre- 
>> install).
>> >
>> > Is this intentional?  If so, why?
>>
>> Shouldn't the PATH include the wrapper directory which provides the
>> libtool wrapper as well?
>
> Indeed, it's supposed to.  Not just that, but pkgsrc is supposed to
> set PATH to include ${LOCALBASE}/bin as well (see usage of
> PREPEND_PATH in bsd.prefs.mk).  minskim, is there actually a problem
> or is this just an observation?

There is.  Depending on the SU_CMD setting and the root users's PATH,  
pkgsrc may fail to run libtool or invoke non-pkgsrc libtool.

Regards,
Min