On Thu, Sep 6, 2012 at 8:45 AM, Stefan Weil<address@hidden> wrote:
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?
It should be if windows is POSIX enough.
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?
...otherwise \n will turn to \r\n? IIRC this behaviour was tunable at the system
level under cygwin. Not under mingw?
Is there a list of such differences?