On 9 January 2011 19:08, Blue Swirl wrote:
> On Sun, Jan 9, 2011 at 5:47 PM, riku voipio wrote:
>> On 01/09/2011 04:47 PM, Blue Swirl wrote:
>>> This fails if the file doesn't exist:
>>> CC i386-linux-user/syscall.o
>>> /src/qemu/linux-user/syscall.c:86:26: error: linux/fiemap.h: No such
>>>
On 01/09/2011 06:47 PM, riku voipio wrote:
> On 01/09/2011 04:47 PM, Blue Swirl wrote:
>> This fails if the file doesn't exist:
>>CCi386-linux-user/syscall.o
>> /src/qemu/linux-user/syscall.c:86:26: error: linux/fiemap.h: No such
>> file or directory
>
>> The fix is to introduce a feature c
On Sun, Jan 9, 2011 at 5:47 PM, riku voipio wrote:
> On 01/09/2011 04:47 PM, Blue Swirl wrote:
>>
>> This fails if the file doesn't exist:
>> CC i386-linux-user/syscall.o
>> /src/qemu/linux-user/syscall.c:86:26: error: linux/fiemap.h: No such
>> file or directory
>
>> The fix is to introduce
On 01/09/2011 04:47 PM, Blue Swirl wrote:
This fails if the file doesn't exist:
CCi386-linux-user/syscall.o
/src/qemu/linux-user/syscall.c:86:26: error: linux/fiemap.h: No such
file or directory
The fix is to introduce a feature check in configure.
Perhaps we can do without configure
On Fri, Jan 7, 2011 at 8:52 PM, Riku Voipio wrote:
> From: Peter Maydell
>
> Implement the FS_IOC_FIEMAP ioctl using the new support for
> custom handling of ioctls; this is needed because the struct
> that is passed includes a variable-length array.
>
> Signed-off-by: Peter Maydell
> Signed-off
From: Peter Maydell
Implement the FS_IOC_FIEMAP ioctl using the new support for
custom handling of ioctls; this is needed because the struct
that is passed includes a variable-length array.
Signed-off-by: Peter Maydell
Signed-off-by: Riku Voipio
---
linux-user/ioctls.h|4 ++
linux
