qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Emmanuel Kasper <emmanuel@libera.cc>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Use of LONG_LONG_MAX breaks build on OSX ?
Date: Sun, 28 Feb 2010 19:07:13 +0100	[thread overview]
Message-ID: <20100228180713.GO10291@volta.aurel32.net> (raw)
In-Reply-To: <4B466C56.5020701@libera.cc>

On Fri, Jan 08, 2010 at 12:20:54AM +0100, Emmanuel Kasper wrote:
> Hello
> Qemu does not build on my platform ( OSX / 10.5 / PowerPC ) because of
> the use of  LONG_LONG_MAX in raw-posix.c
> Replacing LONG_LONG_MAX with LLONG_MAX fixes the build and is more
> standard  IMHO ( LONG_LONG_MAX is GNU libc, LLONG_MAX is C99 standard )
> The following patch makes this trivial switch.

As qemu is not compiled with -std=c99, LLONG_MAX is not guaranteed to be
defined (it is on recent systems, not on old ones). The best solution in
that case is probably to do at the begining of the file:

#ifndef LONG_LONG_MAX
#define LONG_LONG_MAX LLONG_MAX
#endif

Or applying your patch and doing the reverse.

Also please add a Signed-off-by: line.

> --- block-raw-posix.c.before    2010-01-07 22:40:37.000000000 +0100
> +++ block-raw-posix.c   2010-01-07 22:41:43.000000000 +0100
> @@ -782,7 +782,7 @@
>          if (size == 0)
>  #endif
>  #ifdef CONFIG_COCOA
> -        size = LONG_LONG_MAX;
> +        size = LLONG_MAX;
>  #else
>          size = lseek(fd, 0LL, SEEK_END);
>  #endif
> 
> 
> 

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

      reply	other threads:[~2010-02-28 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 23:20 [Qemu-devel] Use of LONG_LONG_MAX breaks build on OSX ? Emmanuel Kasper
2010-02-28 18:07 ` Aurelien Jarno [this message]

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=20100228180713.GO10291@volta.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=emmanuel@libera.cc \
    --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).