On Sat, 2013-05-25 at 18:01 +0200, Geert Uytterhoeven wrote: > On Sat, May 25, 2013 at 5:14 PM, Mark Salter <msalter@xxxxxxxxxx> wrote: > > /* > > * int-ll64 is used practically everywhere now, > > This comment is obsolete, it's used everywhere now. > > > * so use it as a reasonable default. > > */ > > #include <asm-generic/int-ll64.h> > > > > Shouldn't this be: > > > > #include <asm/bitsperlong.h> > > #if __BITS_PER_LONG == 64 > > #include <asm-generic/int-l64.h> > > #else > > #include <asm-generic/int-ll64.h> > > #endif > > No. Inside the kernel, all 64-bit platforms use int-ll64.h. Except for alpha and ia64... > > For backwards compatibility, alpha, ia64, mips, and powerpc (unless > __SANE_USERSPACE_TYPES__ is defined) still use int-l64.h in userspace. > > So it seems your glibc ues the old convention. Any chance you can still > switch? Not glibc, which provides the same stdint.h for all arches. The problem is the namespace pollution caused by the app defining __s64 to be glibc's int64_t. I assume that aarch64 kernel headers pull in the kernel definition of __s64 for some reason where other kernel arches do not. So it is just by luck that fuse builds on the other arches. I think I'll take it up with the fuse maintainers... --Mark -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
