[PATCH] reorder major-0 devices (was Re: [PATCH] implement /proc/sysvipc/*)

2011-04-03 Thread Yaakov (Cygwin/X)
On Fri, 2011-04-01 at 23:33 +0200, Corinna Vinschen wrote: On Apr 1 14:57, Yaakov (Cygwin/X) wrote: For the sake of clarity, I would reorder it a bit further to make FH_PROC and friends to one side of major-0 and everything else to the other side: /* begin /proc directories */

[PATCH] fix make after clean

2011-04-03 Thread Yaakov (Cygwin/X)
If you run make clean in winsup/cygwin followed by make -jX, the build fails because devices.cc is not found; it was removed by make clean but nothing forced it to be regenerated in time. Patch attached. Yaakov 2011-04-03 Yaakov Selkowitz yselkow...@users.sourceforge.net * Makefile.in

[PATCH] make sys/sysmacros.h compatible with glibc

2011-04-03 Thread Yaakov (Cygwin/X)
When building Qt Creator, I encountered a compile error because its code uses 'major' and 'minor' as variable names. Looking at the current sys/sysmacros.h, which is pulled in automatically by sys/types.h, makes it obvious why that doesn't work. Since this code obviously compiles on Linux, I

Re: [PATCH] make sys/sysmacros.h compatible with glibc

2011-04-03 Thread Christopher Faylor
On Sun, Apr 03, 2011 at 06:37:25PM -0500, Yaakov (Cygwin/X) wrote: When building Qt Creator, I encountered a compile error because its code uses 'major' and 'minor' as variable names. Looking at the current sys/sysmacros.h, which is pulled in automatically by sys/types.h, makes it obvious why

[PATCH] add information to /proc/version

2011-04-03 Thread Yaakov (Cygwin/X)
On Linux, /proc/version also displays the username of the kernel compiler and the version of gcc used to compile[1]. This patch does the same for Cygwin: $ cat /proc/version CYGWIN_NT-6.1-WOW64 version 1.7.10(0.238/5/3) (Yaakov@YAAKOV04) (gcc version 4.5.2 (GCC) ) 2011-03-30 18:56 Patches for

Re: [PATCH] make sys/sysmacros.h compatible with glibc

2011-04-03 Thread Yaakov (Cygwin/X)
On Sun, 2011-04-03 at 19:55 -0400, Christopher Faylor wrote: +#define __INSIDE_CYGWIN_GNU_DEV__ I'd prefer a more descriptive name like __DONT_DEFINE_INLINE_GNU_DEV The __INSIDE_CYGWIN_foo__ naming scheme seems to be what is used elsewhere for similar purposes, hence my choice here. but,

Re: [PATCH] fix make after clean

2011-04-03 Thread Yaakov (Cygwin/X)
On Sun, 2011-04-03 at 19:03 -0400, Christopher Faylor wrote: This can't be right. In all of the times that I've run a make clean, I have never needed this. A .o relying on .cc is a given. You don't need an explicit rule. Without it, after a successfully completed build: $ make clean -C

Re: [PATCH] make sys/sysmacros.h compatible with glibc

2011-04-03 Thread Christopher Faylor
On Sun, Apr 03, 2011 at 07:11:51PM -0500, Yaakov (Cygwin/X) wrote: On Sun, 2011-04-03 at 19:55 -0400, Christopher Faylor wrote: +#define __INSIDE_CYGWIN_GNU_DEV__ I'd prefer a more descriptive name like __DONT_DEFINE_INLINE_GNU_DEV The __INSIDE_CYGWIN_foo__ naming scheme seems to be what is

Re: [PATCH] fix make after clean

2011-04-03 Thread Christopher Faylor
On Mon, Apr 04, 2011 at 01:07:27AM -0400, Christopher Faylor wrote: I *am* building on Linux, though, so maybe that's the difference. Nope. It works fine on Windows too. cgf

Re: [PATCH] fix make after clean

2011-04-03 Thread Yaakov (Cygwin/X)
On Mon, 2011-04-04 at 01:07 -0400, Christopher Faylor wrote: On Sun, Apr 03, 2011 at 07:22:42PM -0500, Yaakov (Cygwin/X) wrote: Without it, after a successfully completed build: $ make clean -C i686-pc-cygwin/winsup/cygwin [...] $ make [...goes until winsup/cygwin...] [...compiles all