qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] pixman: remove -Wredundand-decls
Date: Mon, 15 Apr 2013 21:20:29 +1000	[thread overview]
Message-ID: <516BE27D.2060105@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA8xe9DYJZiEpeAWVvHsYkbCVn68HjG7yJ4VxDC_14_4cw@mail.gmail.com>

On 04/15/2013 09:14 PM, Peter Maydell wrote:
> On 15 April 2013 12:08, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>> On 04/15/2013 09:00 PM, Peter Maydell wrote:
>>> You may be hitting more issues because your target libc happens to be
>>> one that not very many other people are targetting.
>>
>>
>> Is standard glibc not popular any more? Wow. Neither RHEL (5.0+) nor Fedora
>> (16, 18) has that _ASSERT_H_DECLS in assert.h. So what is the target for
>> the QEMU people then?
>
> Well, compilation of QEMU against glibc for ppc64 probably
> doesn't get much testing.

assert.h is exactly the same on my thinkpad (x86_64) with fedora18 as all 
(most?) standard headers. If I replace powerpc64-linux-gcc with the 
standard x86_64 gcc, I get the same error.


-- 
Alexey

  reply	other threads:[~2013-04-15 11:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  2:31 [Qemu-devel] [PATCH] pixman: remove -Wredundand-decls Alexey Kardashevskiy
2013-04-15  7:08 ` Markus Armbruster
2013-04-15  7:12   ` Alexey Kardashevskiy
2013-04-15  8:23     ` Markus Armbruster
2013-04-15  9:50       ` Alexey Kardashevskiy
2013-04-15 10:01         ` Peter Maydell
2013-04-15 10:40           ` Peter Maydell
2013-04-15 10:52           ` Alexey Kardashevskiy
2013-04-15 11:00             ` Peter Maydell
2013-04-15 11:08               ` Alexey Kardashevskiy
2013-04-15 11:14                 ` Peter Maydell
2013-04-15 11:20                   ` Alexey Kardashevskiy [this message]
2013-04-15 12:57             ` Markus Armbruster
2013-04-15 13:03               ` Alexey Kardashevskiy
2013-04-15 15:55                 ` Markus Armbruster
2013-04-15 22:48                   ` Alexey Kardashevskiy
2013-04-16  3:16                     ` Alexey Kardashevskiy
2013-04-16  7:57                       ` Markus Armbruster
2013-04-16  9:22                         ` Paolo Bonzini
2013-04-16 10:29                           ` Markus Armbruster
2013-04-16 10:54                           ` Alexey Kardashevskiy
2013-04-16 11:12                             ` Paolo Bonzini
2013-04-16 11:52                               ` Markus Armbruster
2013-04-16  9:00                     ` Markus Armbruster
2013-04-16 10:54                       ` Alexey Kardashevskiy
2013-04-16 11:51                       ` Kevin Wolf
2013-04-16 12:12                         ` Markus Armbruster
2013-04-15  7:18 ` Peter Maydell
2013-04-15  7:26   ` Alexey Kardashevskiy
2013-04-15  7:30     ` Peter Maydell
2013-04-15  7:45       ` Alexey Kardashevskiy

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=516BE27D.2060105@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=armbru@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).