On 02.06.2013 00:35, Peter Maydell wrote:
> The linux-user syscall emulation layer currently supports the openat
> family of syscalls via two mechanisms: simply calling the corresponding
> libc functions, and making direct syscalls. Since glibc has supported
> these functions since at least glibc 2
On 06/01/2013 03:35 PM, Peter Maydell wrote:
> Basically, removing the ugly direct syscall access seemed nicer
> than trying to fix up and render consistent the broken ifdefs :-)
>
> [RHEL5 has glibc2.5 and provides these functions. RHEL4 did not
> but we don't build on RHEL4 anyhow because its gl
The linux-user syscall emulation layer currently supports the openat
family of syscalls via two mechanisms: simply calling the corresponding
libc functions, and making direct syscalls. Since glibc has supported
these functions since at least glibc 2.5, there's no real need to
retain the (essentiall