Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-19 Thread Bruce Evans
On Fri, 18 May 2001, Ruslan Ermilov wrote: > > sbin/mount_null/Makefile > > sbin/mount_portal/Makefile > > sbin/mount_umap/Makefile > > sbin/mount_union/Makefile > > > FS headers should go into /usr/include/fs/fs.h, one per > each filesystem. without a slash? This isn't so clear. Lots of hea

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Peter Wemm
Brian Somers wrote: > John/peter, could you repo-copy src/sys/dev/digi/digiio.h to > src/sys/sys/digiio.h ? Done. > Ta. > > > On Fri, 18 May 2001, Brian Somers wrote: > > > > > > On Thu, 17 May 2001, Warner Losh wrote: > > > > I quite like the fact that the programming interface is > > > > s

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Warner Losh
In message <[EMAIL PROTECTED]> Bruce Evans writes: : On Fri, 18 May 2001, Brian Somers wrote: : : > > On Thu, 17 May 2001, Warner Losh wrote: : > > I quite like the fact that the programming interface is : > > separated from the driver implementation. There is less chance that the : > > driver

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Ruslan Ermilov
On Fri, May 18, 2001 at 05:11:11PM +0300, Ruslan Ermilov wrote: > On Thu, May 17, 2001 at 07:52:51PM +0300, Ruslan Ermilov wrote: > [...] > > > > There are 59 Makefiles that have -I${.CURDIR}/(../)+sys in them. > > All these are bogus. We should get rid of all of them (-I's). > > > > So far, I

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Ruslan Ermilov
On Thu, May 17, 2001 at 07:52:51PM +0300, Ruslan Ermilov wrote: [...] > > There are 59 Makefiles that have -I${.CURDIR}/(../)+sys in them. > All these are bogus. We should get rid of all of them (-I's). > > So far, I have found sbin/mount_* use headers from /sys/miscfs/ > that are not installed

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Brian Somers
John/peter, could you repo-copy src/sys/dev/digi/digiio.h to src/sys/sys/digiio.h ? Ta. > On Fri, 18 May 2001, Brian Somers wrote: > > > > On Thu, 17 May 2001, Warner Losh wrote: > > > I quite like the fact that the programming interface is > > > separated from the driver implementation. Ther

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Bruce Evans
On Fri, 18 May 2001, Brian Somers wrote: > > On Thu, 17 May 2001, Warner Losh wrote: > > I quite like the fact that the programming interface is > > separated from the driver implementation. There is less chance that the > > driver writer will expose irrelavent implementation details in the API,

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Brian Somers
> On Thu, 17 May 2001, Warner Losh wrote: > > > In message <[EMAIL PROTECTED]> Brian > > Somers writes: > > : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd > > : spell digiio.h /usr/include/sys/digi_io.h. > > > > Actually, the more I think about it, the more I like putting it in >

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-18 Thread Doug Rabson
On Thu, 17 May 2001, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Brian > Somers writes: > : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd > : spell digiio.h /usr/include/sys/digi_io.h. > > Actually, the more I think about it, the more I like putting it in > /usr/include/sys

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-17 Thread Ruslan Ermilov
On Thu, May 17, 2001 at 05:37:54PM +0100, Brian Somers wrote: > [cc'd to -arch and not to cvs-committers] > > For anyone that's reading -arch and hasn't seen this on -current, the > thread is discussing userland sources that have -I../../sys in their > Makefile and then #include . > > I think

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-17 Thread Brian Somers
[cc'd to -arch and not to cvs-committers] For anyone that's reading -arch and hasn't seen this on -current, the thread is discussing userland sources that have -I../../sys in their Makefile and then #include . I think everyone agrees that these headers should be made public, the question is `

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> Brian Somers writes: : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd : spell digiio.h /usr/include/sys/digi_io.h. Actually, the more I think about it, the more I like putting it in /usr/include/sys/fooio.h. We have lots of other files there now. Th

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> Brian Somers writes: : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd : spell digiio.h /usr/include/sys/digi_io.h. We're not solaris :-). BSD traditionally spells things fooio.h for driver foo. FreeBSD changed the traditional place for devices, so o

Where to put include files (was: cvs commit: src Makefile.inc1)

2001-05-17 Thread Brian Somers
> > Most headers that define ioctls are in . I think there should > > be at most one directory for ioctl headers and it shouldn't be a subdir > > of /usr/include/sys (/usr/include/sys/dev doesn't even reflect the > > kernel tree). > > > Might I guess it should probably be called /usr/include/sys