Subject: pkg/7006: namespace conflict: SYS_INCLUDE
To: None <gnats-bugs@gnats.netbsd.org>
From: None <woferry@iname.com>
List: netbsd-bugs
Date: 02/15/1999 01:22:45
>Number:         7006
>Category:       pkg
>Synopsis:       namespace conflict: SYS_INCLUDE
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 15 01:35:01 1999
>Last-Modified:
>Originator:     William O Ferry
>Organization:
	
>Release:        <NetBSD-current source date> SUPed 02/14/1999 16:45 PST
>Environment:
	
System: NetBSD warp.wofme.com 1.3H NetBSD 1.3H (kernel) #1: Sun Oct 18 15:32:03 PDT 1998 root@Ludicrous:/.u1/work/kernel i386


>Description:
	
bsd.kinc.mk uses a variable SYS_INCLUDE, which it expects to have the value of
either "copies" or "symlinks".  cross.mk (in pkgsrc/cross/COMMON) sets this
same variable to be a path for include files.  If you set SYS_INCLUDE in
/etc/mk.conf, the value set here overrides the path set in cross.mk.
>How-To-Repeat:
	
	Set SYS_INCLUDE=copies in /etc/mk.conf, build one of the cross/
packages with a read-only source tree, watch the build fail when cross.mk
tries to create the directories "copies", "copies/machine", and "copies/sys" in
the cross directory.  It will successfully create these directories if cross is
not read-only, I am not sure if the build will work or if things will still go
wrong.
>Fix:
	
	As a workaround I commented out the SYS_INCLUDE line in /etc/mk.conf,
and the cross package built just fine.

	Seems one of these two variables should be changed.  I would imagine
it is easier to change the one in cross.mk, as it seems to be internal to this
file, while the other SYS_INCLUDE is used / referenced in several places.  I'll
let somebody else decide what this variable should be renamed to.  =)
>Audit-Trail:
>Unformatted:
bsd.kinc.mk and cross.mk both use SYS_INCLUDE, expecting different values