Messages in this thread | | | From | David Howells <> | Subject | Re: linux-next: build failure after merge of the vfs tree | Date | Tue, 18 Sep 2018 23:17:21 +0100 |
| |
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > After merging the vfs tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use in this function); did you mean 'fsinfo'?
I think the problem is that I haven't allocated system call numbers for any arches other than x86 - even the x86 syscall numbers are provisional until the patchset is taken upstream. I'm not sure of the best way to deal with this - make the samples dependent on the X86 arch?
> > samples/vfs/test-fsinfo.c:180:30: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=] > > printf("\tmax file size: %llx\n", f->max_file_size);
Sigh. On powerpc __u64 is unsigned long, but on x86_64 it's unsigned long long. Is it possible to shift all arches to use unsigned long long for __u64?
David
| |