>Number:         21634
>Category:       pkg
>Synopsis:       Once again, libtool won't build if mk.conf sets CC or CFLAGS with spaces in them, even if quoted.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 21 07:23:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Thor Lancelot Simon
>Release:        NetBSD-current as of 2003-05-10; pkgsrc as of 2003-05-21
>Organization:
>Environment:
NetBSD this 1.6S NetBSD 1.6S (THIS) #6: Thu May 15 22:58:04 EDT 2003 root@this:/usr/src/sys/arch/i386/compile/THIS i386
Architecture: i386
Machine: i386
>Description:
Trying to rebuild my packages with gcc-3.2.2, I discovered that I could build
almost nothing because libtool-base wouldn't build; it cannot handle the
"-march=athlon-tbird -pipe" argument to gcc I added to my mk.conf.  It can't
handle it if I set CC to just "/usr/pkg/gcc-3.2.2/bin/cc" and set CFLAGS+= the
options, either, and it can't handle the argument whether quoted (or even
quoted with \") or not.

A lot of effort has repeatedly been put into making sure this works, but it
has repeatedly been re-broken.  The inability to add optimization or tuning
flags to the compilation command for package builds is a severe annoyance
for those trying to run large numerical jobs on NetBSD; in fact, in prior
instances of this brokenness, I know of at least two users who gave up in
a huff and went back to using Linux.

>How-To-Repeat:
	Just put a space in your CC= in your /etc/mk.conf and try to build
libtool-base from today's pkgsrc.
>Fix:
	Regression test this when tinkering with important things like the
        pkgsrc .mk files, buildlink, or libfool.

>Release-Note:
>Audit-Trail:
>Unformatted: