From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] w64: Don't redefine lseek, ftruncate
Date: Sat, 10 Mar 2012 13:11:00 +0100 [thread overview]
Message-ID: <4F5B44D4.5030105@suse.de> (raw)
In-Reply-To: <1331374472-15157-1-git-send-email-sw@weilnetz.de>
Am 10.03.2012 11:14, schrieb Stefan Weil:
> MinGW-w64 already defines lseek and ftruncate (and uses the 64 bit
> variants). The conditional compilation avoids redefinitions
> (which would be wrong) and compiler warnings.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> qemu-common.h | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-common.h b/qemu-common.h
> index dbfce6f..b0fdf5c 100644
> --- a/qemu-common.h
> +++ b/qemu-common.h
> @@ -93,9 +93,13 @@ typedef int (*fprintf_function)(FILE *f, const char *fmt, ...)
>
> #ifdef _WIN32
> #define fsync _commit
> -#define lseek _lseeki64
> +#if !defined(lseek)
> +# define lseek _lseeki64
> +#endif
> int qemu_ftruncate64(int, int64_t);
> -#define ftruncate qemu_ftruncate64
> +#if !defined(ftruncate)
> +# define ftruncate qemu_ftruncate64
> +#endif
lseek looks okay to me, but did you check that ftruncate and
qemu_ftruncate64 behave the same?
Andreas
>
> static inline char *realpath(const char *path, char *resolved_path)
> {
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-10 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 10:14 [Qemu-devel] [PATCH] w64: Don't redefine lseek, ftruncate Stefan Weil
2012-03-10 10:14 ` [Qemu-devel] [PATCH] configure: Test for libiberty.a (mingw32) Stefan Weil
2012-03-10 16:28 ` Andreas Färber
2012-03-10 18:47 ` Stefan Weil
2012-03-11 16:10 ` Blue Swirl
2012-03-10 12:11 ` Andreas Färber [this message]
2012-03-10 16:17 ` [Qemu-devel] [PATCH] w64: Don't redefine lseek, ftruncate Stefan Weil
2012-03-11 16:09 ` 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=4F5B44D4.5030105@suse.de \
--to=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).