Re: Cross-compiling L4Re for MIPS32

On Monday 20. June 2016 23.01.51 Adam Lackorzynski wrote:
> On Thu Jun 16, 2016 at 00:10:50 +0200, Paul Boddie wrote:
> > 
> > make O=mybuild config
> 
> Do you have linux-libc-dev:amd64 installed? If not, please do.

Is this necessary if I'm using the i386 host architecture in Debian? I think I 
posted the following earlier:

dpkg -S /usr/include/asm-generic/unistd.h
linux-libc-dev:i386, linux-libc-dev:mipsel: /usr/include/asm-generic/unistd.h

So, I have two architecture variants of the package installed already.

Although architecture-specific unistd.h files are provided by a surprising 
number of packages [*], I don't see any difference in behaviour between them 
with regard to this issue. For example:

diff /usr/mipsel-linux-gnu/include/asm-generic/unistd.h /usr/include/asm-
generic/unistd.h 
715a716,723
> #define __NR_mlock2 284
> __SYSCALL(__NR_mlock2, sys_mlock2)
> #define __NR_copy_file_range 285
> __SYSCALL(__NR_copy_file_range, sys_copy_file_range)
> #define __NR_preadv2 286
> __SC_COMP(__NR_preadv2, sys_preadv2, compat_sys_preadv2)
> #define __NR_pwritev2 287
> __SC_COMP(__NR_pwritev2, sys_pwritev2, compat_sys_pwritev2)
718c726
< #define __NR_syscalls 284
---
> #define __NR_syscalls 288

They both exclude the required definitions without __ARCH_WANT_SYSCALL_NO_AT.

Paul

[*] 
https://packages.debian.org/search?searchon=contents&keywords=gnu%2Finclude%2Fasm-
generic%2Funistd.h&mode=path&suite=unstable&arch=any