qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Build failure on OS X
Date: Sun, 30 Sep 2007 14:17:02 +0200	[thread overview]
Message-ID: <1191154622.29900.118.camel@rapid> (raw)
In-Reply-To: <494D52E6-D90D-4426-A866-8D413F9333B6@web.de>

On Sun, 2007-09-30 at 14:05 +0200, Andreas Färber wrote:
> Hi,
> 
> Am 30.09.2007 um 13:45 schrieb J. Mayer:
> 
> >> Anyone any idea what might've caused this build failure? I'm fairly
> >> certain I haven't messed with or updated the system headers.
> >
> > have you just updated your CVS co ?
> 
> Yes.
> 
> > Please try to comment the "always_inline" definition in vl.h /
> > exec-all.h.
> > If this is what's breaking your build, I'll revert this definition.
> 
> It is, thanks for the pointer! (The source file itself didn't appear  
> to have been updated.)
> 
> >> With line 284 of math.h reading:
> >> 		static __inline__ int __inline_isfinitef	(float      )
> >> __MATH_H_ALWAYS_INLINE__;
> >
> > The fact the error mentions "__attribute__" and ALWAYS_INLINE make me
> > think the always_inline defintion is the suspect here....
> 
> I believe Apple's GCC in general has a problem with the __attribute__  
> notation. The ppc*-softmmu fail to build for some time due to its use  
> for aliasing in hw/ppc.c. Maybe we could add a configure check for  
> this feature to have a conditional define? That would allow a more  
> elegant fix than the one I use locally and had previously suggested.

Sorry for introducing this problem...
Would this new definition solve the compilation failure ?

#ifndef always_inline
#if (__GNUC__ < 3) || defined(__APPLE__)
#define always_inline inline
#else
#define always_inline __attribute__ (( always_inline )) inline
#endif
#endif

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2007-09-30 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 10:09 [Qemu-devel] Build failure on OS X Andreas Färber
2007-09-30 11:45 ` J. Mayer
2007-09-30 12:05   ` Andreas Färber
2007-09-30 12:17     ` J. Mayer [this message]
2007-09-30 13:08       ` Andreas Färber
2007-09-30 13:27         ` J. Mayer
2007-09-30 14:28           ` Andreas Färber
2007-09-30 14:37             ` J. Mayer
2007-09-30 15:05               ` Andreas Färber
2007-09-30 15:54                 ` Andreas Färber
2007-10-03 11:12                   ` Andreas Färber
2007-10-01  2:36                 ` J. Mayer

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=1191154622.29900.118.camel@rapid \
    --to=l_indien@magic.fr \
    --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).