Matthew Dillon writes: > > :WARNS=5. > > This isn't helpful. I tried adding every -W switch in bsd.sys.mk > and couldn't reproduce the problem. What compiler option is causing > the problem?
I don't know which specific one. > Ok, now I'm really confused. How can it not always help? If the > arguments are the same as the arguments declared in the underlying > procedures why would an error still be produced? The diff you produced > for proc.h is *already* fairly extensive. If you want to fix this, > you only need to fix the lines generating compiler warnings. "arg" in a function prototype gets confused with variable "arg" in some function(s). > I really dislike screwing around with source code to work around > bugs in the the compiler, or lint. Given the choice of underlines > or leaving the arguments unnamed, I would leave them unnamed. Or I > would figure out and remove whatever broken compiler option is generating > the warning in the first place. Then can we just get the proc.h prototypes into a (any) consistent style? M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
