All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com, "He,
	Qing" <qing.he@intel.com>
Subject: Re: ioemu build failure with GCC > 4.3
Date: Thu, 10 Jul 2008 10:43:17 +0100	[thread overview]
Message-ID: <20080710094317.GE23601@redhat.com> (raw)
In-Reply-To: <C49B9763.23DA8%keir.fraser@eu.citrix.com>

On Thu, Jul 10, 2008 at 10:39:31AM +0100, Keir Fraser wrote:
> On 10/7/08 10:32, "He, Qing" <qing.he@intel.com> wrote:
> 
> > It's most straightforward to remove `inline' in slirp/misc.c, the code
> > doesn't really seem to benefit from it. But it looks pretty old and not
> > maintained for sometime. What about patch it locally?
> > 
> > Other options include specify `-fgnu89-inline' (n/a prior to GCC 4.1.3)
> > and overrides slirp compile line with `-std=gnu89', but may not be
> > preferred.
> 
> Could we change the '#define inline' in slirp_config.h to define it to
> nothing? None of the usages of 'inline' in the slirp directory look like a
> particularly good idea.

None of the entire slirp directory looks like a good idea. This code
isn't even used in Xen is it ? My vote  would be disabling compilation
of entire slirp directory for Xen. 

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2008-07-10  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  9:32 ioemu build failure with GCC > 4.3 He, Qing
2008-07-10  9:39 ` Keir Fraser
2008-07-10  9:43   ` Daniel P. Berrange [this message]
2008-07-10  9:44     ` Ian Jackson
2008-07-10  9:49       ` Ian Jackson
2008-07-10 13:18         ` Ross Philipson
2008-07-10 14:06           ` Ian Jackson
2008-07-10 14:13             ` Ross Philipson
2008-07-14 15:12               ` Ian Jackson
2008-07-14 15:21                 ` Stefan de Konink
2008-07-15 13:55                   ` Ross Philipson
2008-07-15 14:06                     ` Keir Fraser
2008-07-15 14:09                       ` Ross Philipson
2008-07-15 18:33                         ` [PATCH] " Espen Skoglund
2008-07-15 18:45                         ` Espen Skoglund
2008-07-14 16:56                 ` prashanth.mundkur

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=20080710094317.GE23601@redhat.com \
    --to=berrange@redhat.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=qing.he@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.