We use it in bitops/__ffs.h and bitops/atomic.h, that we also got from the kernel, but were getting it from either newer systems that carry it in /usr/include, or from the kernel sources, that we decided not to touch from tools/ code. Fix it.
Showing the changes to tools/include/uapi (1 of 21 files). Show all
Unified · Split
| @@ -0,0 +1,15 @@ | ||
| 1 | +#ifndef _UAPI__ASM_GENERIC_BITS_PER_LONG | |
| 2 | +#define _UAPI__ASM_GENERIC_BITS_PER_LONG | |
| 3 | + | |
| 4 | +/* | |
| 5 | + * There seems to be no way of detecting this automatically from user | |
| 6 | + * space, so 64 bit architectures should override this in their | |
| 7 | + * bitsperlong.h. In particular, an architecture that supports | |
| 8 | + * both 32 and 64 bit user space must not rely on CONFIG_64BIT | |
| 9 | + * to decide it, but rather check a compiler provided macro. | |
| 10 | + */ | |
| 11 | +#ifndef __BITS_PER_LONG | |
| 12 | +#define __BITS_PER_LONG 32 | |
| 13 | +#endif | |
| 14 | + | |
| 15 | +#endif /* _UAPI__ASM_GENERIC_BITS_PER_LONG */ | |