From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: qemu-devel@nongnu.org, "Andreas Färber" <andreas.faerber@web.de>
Subject: Re: [Qemu-devel] build error
Date: Tue, 8 Jan 2008 17:53:33 +0100 [thread overview]
Message-ID: <20080108165333.GE18933@edgar.se.axis.com> (raw)
In-Reply-To: <0ACF5616-6FC6-4E44-8679-A5F44BAA0312@web.de>
On Tue, Jan 08, 2008 at 03:43:34PM +0100, Andreas Färber wrote:
> Hello,
>
> Am 08.01.2008 um 00:59 schrieb Rob Landley:
>
>> On Monday 07 January 2008 05:27:19 Edgar E. Iglesias wrote:
>>> I needed this or similar to build recent qemu's with gcc-4.
>>>
>> Is that all you needed, and did the result work?
>
> For system emulation on OSX/ppc I only needed a fix for always_inline (as
> suggested by Alexander Graf as part of his OSX x86_64 patch), then
> sparc-softmmu compiles and runs fine for several hours on OSX Leopard.
>
> It seems Leopard's system headers are incompatible with gcc-3.3, and using
> a different -sdkroot does not work. So GCC4 is becoming a necessity there,
> too (in addition to any OSX/i386).
>
> Is there anything specific to watch out for with GCC4 at this time? What
> does this ".previous" addition fix?
The workaround in linux-user/main.c for recent libc's switches the current section to .rodata but does not switch it back. The .previous makes sure it is restored to it's previous section.
It's not really gcc4 related but on my system gcc 4 failed while gcc-3.4.6 didn't.
Best regards
--
Edgar E. Iglesias
Axis Communications AB
prev parent reply other threads:[~2008-01-08 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:27 [Qemu-devel] build error Edgar E. Iglesias
2008-01-07 23:59 ` Rob Landley
2008-01-08 10:42 ` Edgar E. Iglesias
2008-01-08 14:43 ` Andreas Färber
2008-01-08 16:53 ` Edgar E. Iglesias [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=20080108165333.GE18933@edgar.se.axis.com \
--to=edgar.iglesias@axis.com \
--cc=andreas.faerber@web.de \
--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).