site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On May 8, 2006, at 4:27 AM, Peter Lovell wrote: Ok, I feel dumb asking this, but I can't seem to find it, so... That's the correct file, if you want to let things build with warnings. bsd/vfs/vfs_subr.c and bsd/sys/vnode.h Which is what I'd recommend. -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On May 7, 2006, at 4:09 PM, rick@snowhite.cis.uoguelph.ca wrote: I've added a bunch of dirs to xnu-792 and the make finds them and builds them ok. (added to bsd/conf/files) However, as soon as I get a warning on any of them, the build stops. I can see that other parts of the system build with warnings and keep going. So, what's the trick to get the build environment to not stop on warnings? (I'm building on Darwin8.0.1 for i386, if that makes any difference.) I have succeeded in getting rid of the warnings, but had to add crud like the following to avoid the warnings, which isn't exactly pretty:-) /* XXX really dumb, but the compiler complains since the last arg * of vnode_waitforwrites() isn't "const char *". */ bcopy("nfsflush", stupid, 9); while ((error = vnode_waitforwrites(vp, 0, slpflag, slptimeo, stupid))) { Thanks in advance for any help, rick Hi Rick, have a look at xnu/bsd/conf/Makefile.i386 for the list of files for OBJS_NO_WERROR If you add your files to the list then the build will warn but not stop. I know it looks weird but this file with "i386" suffix is used for ppc builds. He's actually doing an i386 build... in 792, this is only the case for the i386 code anyway (which makes warnings errors for everything except the listed files). Alternately, you can change the last argument to vnode_waitforwrites() to a const char * by modifying In general, if you are getting warnings, then it's best, particularly for new files which haven't been vetted, for them to be treated as errors. This email sent to site_archiver@lists.apple.com