>Number:         17052
>Category:       pkg
>Synopsis:       When gcc is used when a package build, the /etc/mk.conf
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun May 26 13:39:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Mipam
>Release:        1.4.3
>Organization:
Mipam & Co :-)
>Environment:
System: NetBSD 1.4.3A NetBSD 1.4.3A (Mipam) #0: Fri Mar 15 00:56:57 CET 2002 root@:/usr/src/sys/arch/i386/compile/Mipam i386


>Description:
	Suppose you got CFLAGS=-pipe in your /etc/mk.conf
	normally this option is always taken when a package builds.
	However, when a package uses gcc instead of the default cc
	then the mk.conf doesnt seem to be consulted for compilation options.
	For example the postfix package wants to use gcc, and doesnt
	use the CFLAGS options which i specified in /etc/mk.conf
>How-To-Repeat:
	echo CFLAGS=-pipe >> /etc/mk.conf 
	and build the postfix package  for example.
	I encountered this at more packages which i cant recall all right now.
>Fix:
	explictly put it in the gcc options of the makefile or even in the
	files to compile. 
>Release-Note:
>Audit-Trail:
>Unformatted:
 options arent taken.