From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compilation broken in SVN version and a debug register question
Date: Sun, 04 May 2008 21:29:01 +0400 [thread overview]
Message-ID: <481DF25D.8070009@wasp.net.au> (raw)
In-Reply-To: <cef699d70805040929x14f1c235idc47d2e66554bb8e@mail.gmail.com>
Ben Taylor wrote:
> On Wed, Apr 23, 2008 at 8:34 AM, Balazs Attila-Mihaly (Cd-MaN)
> <x_at_y_or_z@yahoo.com> wrote:
>> Hello all.
>>
>> I fail to compile the version 4242 from the SVN (which I checked out ~1 hour ago). On an Ubuntu 7.10 host with gcc-3.4 and ./configure --target-list=i386-softmmu, I get the following error:
>>
<snip>
>
> The following patch should fix the compilation of op.c and helper.c.
>
> This been tested on solaris x86 (32/64 bit) and Ubuntu 7.10 (32-bit). When
> configuring on the 32-bit systems, I used --extra-cflags="-march=i686
> -mtune=i686"
> and both spill errors in op.c and helper.c are gone, and the binaries
> will boot Milax (a Solaris based DamnSmallLinux clone)
On ubuntu...
apt-get remove gcc-3.4
apt-get install gcc-3.3
.. effectively worked around the issue for me.
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2008-05-04 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 12:34 [Qemu-devel] Compilation broken in SVN version and a debug register question Balazs Attila-Mihaly (Cd-MaN)
2008-04-23 17:09 ` Blue Swirl
2008-05-04 16:29 ` Ben Taylor
2008-05-04 17:29 ` Brad Campbell [this message]
2008-05-04 17:31 ` Ben Taylor
2008-05-04 19:45 ` Aurelien Jarno
2008-05-04 19:57 ` Ben Taylor
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 5:19 Balazs Attila-Mihaly (Cd-MaN)
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=481DF25D.8070009@wasp.net.au \
--to=brad@wasp.net.au \
--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).