Subject: Re: kern/30425: genassym usage failure in kernel building after May 2005 changes
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: List Mail User <track@Plectere.com>
List: netbsd-bugs
Date: 06/04/2005 19:58:02
The following reply was made to PR kern/30425; it has been noted by GNATS.

From: List Mail User <track@Plectere.com>
To: gnats-bugs@NetBSD.org
Cc: track@Plectere.com
Subject: Re: kern/30425: genassym usage failure in kernel building after May 2005 changes
Date: Sat, 4 Jun 2005 12:57:34 -0700 (PDT)

 >...
 >>Number:         30425
 >>Category:       kern
 >>Synopsis:       genassym is not used properly anymore in sys/conf/Makefile.kern.inc
 >>Confidential:   no
 >>Severity:       non-critical
 >>Priority:       low
 >>Responsible:    kern-bug-people
 >>State:          open
 >>Class:          sw-bug
 >>Submitter-Id:   net
 >>Arrival-Date:   Sat Jun 04 10:20:00 +0000 2005
 >>Originator:     Geoff C. Wing
 >>Release:        NetBSD 3.99.5 (2005-06-03)
 >>Organization:
 >>Environment:
 >System: NetBSD g.primenet.com.au 3.99.5 NetBSD 3.99.5 (G) #0: Mon May 30 14:02:30 EST 2005 gcw@g.primenet.com.au:/usr/netbsd/src/sys/arch/i386/compile/G i386
 >Architecture: i386
 >Machine: i386
 >>Description:
 >	The changes in how genassym is used to build assym.h for a kernel
 >	causes problems with unknown kernel options having spaces or
 >	globbing characters
 >	e.g. in a kernel config I have ``options MSGBUFSIZE="(32 * 1024)"''.
 >
 >	Unfortunately this is converted to  -DMSGBUFSIZE="(32 * 1024)"
 >	when passed through the compilation.  genassym gets it and expands
 >	it to
 >	    -DMSGBUFSIZE=( {...every file in the compile dir...} 1024)
 >
 >>How-To-Repeat:
 >	add the line above.  Try it.
 >>Fix:
 >	I'll think about it in a bit if nobody else does.
 >
 >
 	Not a fix, but the trivial workaround of using:
 
 options MSGBUFSIZE="(8*NBPG)"
 
 	or anything similar without the spaces or by escaping the wildcard
 character as in:
 
 options MSGBUFSIZE="(8 \* NBPG)"
 
 does function as expected (of course, the first example depends on the lack
 of any file which matches the still potentially expanded wildcard).
 
 	This does not mean that the bug doesn't exist or shouldn't be fixed;
 It is a "regression, since it used to work:  Just I have such a line in nearly
 every kernel config file I use.
 
 
 	Paul Shupak
 	track@plectere.com