From: Stefan Weil <sw@weilnetz.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-xtensa: fix missing errno codes for mingw32
Date: Thu, 06 Sep 2012 06:45:38 +0200 [thread overview]
Message-ID: <50482A72.5020907@weilnetz.de> (raw)
In-Reply-To: <1346891806-13792-1-git-send-email-jcmvbkbc@gmail.com>
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 <jcmvbkbc@gmail.com>
> ---
>
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
next prev parent reply other threads:[~2012-09-06 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 0:36 [Qemu-devel] [PATCH] target-xtensa: fix missing errno codes for mingw32 Max Filippov
2012-09-06 4:45 ` Stefan Weil [this message]
2012-09-06 12:48 ` Max Filippov
2012-09-07 20:22 ` Stefan Weil
2012-09-07 21:20 ` Max Filippov
2012-09-08 9:07 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50482A72.5020907@weilnetz.de \
--to=sw@weilnetz.de \
--cc=blauwirbel@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).