If linux/include/asm-arm/posix_types.h and glibc2.1 <bits/types.h> both want to define __FD_SET in conflicting ways, which one is the implementation? Who owns the toes? Who is doing the treading? :-) And how do I fix it so that things compile (defining __USE_XOPEN is cheating)? Nick unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
- 2.2.2-rmk2 crash on boot Timothy Baldwin
- Re: 2.2.2-rmk2 crash on boot Nicholas Clark
- Re: 2.2.2-rmk2 crash on boot Philip Blundell
- Is char signed or unsigned ? Zsolt Kiraly
- Re: Is char signed or unsi... Russell King
- Re: Is char signed or unsi... Philip Blundell
- Re: Is char signed or unsi... Dr. David Alan Gilbert
- Re: 2.2.2-rmk2 crash on boot Russell King - ARM Linux Admin
- Re: 2.2.2-rmk2 crash on boot Russell King - ARM Linux Admin
- Re: 2.2.2-rmk2 crash on bo... Timothy Baldwin
- Re: __FD_SET Nicholas Clark
- Re: __FD_SET Philip Blundell
- Re: __FD_SET Nicholas Clark
- Re: __FD_SET Philip Blundell
- Re: 2.2.2-rmk2 crash ... Nicholas Clark
- Re: 2.2.2-rmk2 cr... Russell King - ARM Linux Admin
- Re: 2.2.2-rmk2 crash ... Timothy Baldwin
- Re: 2.2.2-rmk2 cr... Russell King
- Re: 2.2.2-rmk... Timothy Baldwin
- Re: 2.2.2-rmk... Russell King - ARM Linux Admin
- Re: 2.2.2-rmk... Timothy Baldwin
