From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Michael Matz <matz@suse.de>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [patch] make qemu work with GCC 4
Date: Wed, 29 Aug 2007 13:40:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708291337440.28586@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291340550.23011@wotan.suse.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1618 bytes --]
Hi,
On Wed, 29 Aug 2007, Michael Matz wrote:
> On Wed, 29 Aug 2007, Johannes Schindelin wrote:
>
> > > The whole patch is against a 0.9.0-cvs version from 2007-07-09 (Alex
> > > might know the exact checkout date), so chances are that it still
> > > applies :)
> >
> > It is based on the z80 fork, but it applies relatively cleanly (one
> > trailing whitespace) to the version as of "Use unsigned 32-bit load
> > for ld/lduw".
> >
> > However, I still get this error:
> >
> > ../dyngen -o op.h op.o
> > dyngen: ret or jmp expected at the end of op_tadd_T1_T0_ccTV
> > make[1]: *** [op.h] Fehler 1
> > make[1]: Leaving directory `/home/me/qemu/sparc-linux-user'
>
> Using SuSE 10.2, i.e. gcc 4.1.2?
Yep. It would be good to fix this error before applying the patch to CVS
;-)
> > When only making i386-softmmu, I still get this (on SuSE 10.2):
> >
> > In file included from /home/gene099/my/qemu/usb-linux.c:29:
> > /usr/include/linux/usbdevice_fs.h:49: error: expected ‘:’, ‘,’, ‘;’, ‘}’
> > or ‘__attribute__’ before ‘*’ token
> > [...]
>
> Yes, that's a problem of the kernel headers on 10.2. You can work
> around this with the below snippet.
I did it differently now.
My changes can be seen (and fetched) at
http://repo.or.cz/qemu/dscho.git/
in the "gcc4" branch. This is just your patch applied to the revision I
mentioned (which is available in the "gcc4-original" branch), then rebased
onto current CVS (or what Jens Axboe's clone is current at right now). I
adjusted one target_ulong, and added another commit for the
linux/compiler.h issue.
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-29 12:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 19:57 [Qemu-devel] [patch] make qemu work with GCC 4 Michael Matz
2007-08-29 8:41 ` Andreas Färber
2007-08-29 11:40 ` Michael Matz
2007-08-29 13:14 ` Andreas Färber
2007-08-29 13:30 ` Michael Matz
2007-08-29 13:59 ` Mulyadi Santosa
2007-08-29 14:11 ` Johannes Schindelin
2007-08-29 16:40 ` Michael Matz
2007-08-29 16:55 ` Johannes Schindelin
2007-08-29 18:09 ` Blue Swirl
2007-08-30 12:46 ` Carlo Marcelo Arenas Belon
2007-08-29 13:59 ` Johannes Schindelin
2007-08-29 14:13 ` Ronald
2007-08-29 14:19 ` Johannes Schindelin
2007-08-29 14:38 ` Andreas Färber
2007-08-29 14:27 ` Andreas Färber
2007-08-29 11:08 ` Johannes Schindelin
2007-08-29 11:46 ` Michael Matz
2007-08-29 12:40 ` Johannes Schindelin [this message]
2007-08-29 15:06 ` Paul Brook
2007-08-29 17:29 ` Michael Matz
2007-08-30 16:52 ` Michael Matz
2007-08-29 18:08 ` Anthony Liguori
2007-08-30 20:28 ` Thiemo Seufer
2007-08-31 13:31 ` Michael Matz
2007-08-31 14:17 ` Thiemo Seufer
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=Pine.LNX.4.64.0708291337440.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=agraf@suse.de \
--cc=matz@suse.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).