Subject: pkg/18371: wm/fvwm2's default CPP path point to the path in build work area
To: None <gnats-bugs@gnats.netbsd.org>
From: None <shigeya@omnisci.co.jp>
List: netbsd-bugs
Date: 09/22/2002 10:48:39
>Number: 18371
>Category: pkg
>Synopsis: wm/fvwm2's FvwmCPP module binary points to package build work area path
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Sep 21 18:50:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Shigeya Suzuki
>Release: NetBSD 1.6
>Organization:
Omnisci Software, Inc.
>Environment:
System: NetBSD firepower-vm.lt.shigeya.org 1.6 NetBSD 1.6 (GENERIC) #4: Sun Sep 15 00:23:29 JST 2002 root@firepower-vm.lt.shigeya.org:/usr/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
When build try to locate CPP, it search for the directory in PATH and
other default area (as written in configure.in). It seems to me that
in a configuration process, .buildlink directories are prepended to PATH,
thus configure find CPP in /usr/pkgsrc/wm/fvwm2/work/.buildlink/bin/cpp by
mistake. Then, on build of FvwmCPP, it includes this path into binary, and
use it as default.
>How-To-Repeat:
use FvwmCPP without specifying cpp path by -cpp option.
>Fix:
Override FVWM_CPP variable in Makefile.
It is easy to provide temporary fix, but since I'm not used to package
build process, I can't provide best way to solve this problem.
One of the option may be patch to configure.in to exclude search in
.buildlink/bin.
>Release-Note:
>Audit-Trail:
>Unformatted: