>Number:         22773
>Category:       pkg
>Synopsis:       /usr/pkg/gcc3/mk/c.mk defines USE_GCC3 which creates dependency on gcc3 pkg instead of gcc3-c
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Sep 13 11:57:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     john@johnrshannon.com
>Release:        NetBSD 1.6Z
>Organization:
	johnrshannon.com
>Environment:
System: NetBSD laptop.mobile.johnrshannon.com 1.6Z NetBSD 1.6Z (KERNEL.new) #7: Fri Sep 12 18:50:01 MDT 2003 root@laptop.mobile.johnrshannon.com:/usr/obj/usr/src/sys/arch/i386/compile/KERNEL.new i386
Architecture: i386
Machine: i386
>Description:
	Two packages will build a gcc3 c compiler: 1) gcc3, and 2) gcc3-c. These two packages install
	to different locations. gcc3-c creates an indirect buildlink dependancy on gcc3. Defining USE_GCC3,
	as is done in pkg/gcc3/mk/c.mk (nominal install location for gcc3-c), includes pkgsrc/gcc3/buildlink2.mk,
	the buildlink file for the other gcc3 package. This creates problems for software that wants
	to use gcc3-c or gcc3-c++.
>How-To-Repeat:
	
>Fix:
	Can be fixed in several places, but I would modify mk/compiler.mk or consider eliminating pkgsrc/gcc3
	and use the incremental gcc3 compiler front-end structure of gcc3-c, gcc3-c++, and gcc3-ada.
>Release-Note:
>Audit-Trail:
>Unformatted: