[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] target-xtensa: fix missing errno codes for ming
From: |
Stefan Weil |
Subject: |
Re: [Qemu-devel] [PATCH] target-xtensa: fix missing errno codes for mingw32 |
Date: |
Thu, 06 Sep 2012 06:45:38 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0 |
Am 06.09.2012 02:36, schrieb Max Filippov:
Put the following errno value mappings under #ifdef:
xtensa-semi.c: In function 'errno_h2g':
xtensa-semi.c:113: error: 'ENOTBLK' undeclared (first use in this function)
xtensa-semi.c:113: error: (Each undeclared identifier is reported only once
xtensa-semi.c:113: error: for each function it appears in.)
xtensa-semi.c:113: error: array index in initializer not of integer type
xtensa-semi.c:113: error: (near initialization for 'guest_errno')
xtensa-semi.c:124: error: 'ETXTBSY' undeclared (first use in this function)
xtensa-semi.c:124: error: array index in initializer not of integer type
xtensa-semi.c:124: error: (near initialization for 'guest_errno')
xtensa-semi.c:134: error: 'ELOOP' undeclared (first use in this function)
xtensa-semi.c:134: error: array index in initializer not of integer type
xtensa-semi.c:134: error: (near initialization for 'guest_errno')
Signed-off-by: Max Filippov <address@hidden>
---
Is semi hosting a useful feature when QEMU runs on a Windows host?
If not, you could conditionally compile the whole semi hosting code
for non Windows only.
If yes, what about the differences in system calls between UNIX like
operating systems and Windows? Should the code for 'open' add O_BINARY?
Regards,
Stefan