Philip Boulain wrote:
> Well done, guys. Someone's trying to build CVS QEMU on gcc4, and you're
> flaming them. This'll really encourage people to work on making
> development versions of QEMU work with gcc4.
May I recommend to everybody involved to cool down a bit?
Working on converting more o
On Friday 14 March 2008 07:59:28 am Rick Vernam wrote:
> And it is necessary to have configure require a special step to build with
> gcc4 anyway.
necessary, as in a very good idea.
necessary to inform those who might not otherwise know...
On Friday 14 March 2008 06:07:37 am Andreas Färber wrote:
> > So I absolutely _fail_ to understand what you thought, implying that
> > I was
> > restricting platform variability.
>
> So in fact you do agree with Rick on that part and replied to the
> 'wrong' message, creating minor confusion: I
> WTF? Rick suggested removing that configure message that you need to
> explicitely override its quite sane default to refuse work with gcc4,
> because at least one platform (the most common one) has problems with it.
I did? where? when? You might have mis-read something.
>
> I was against rem
Well done, guys. Someone's trying to build CVS QEMU on gcc4, and
you're flaming them. This'll really encourage people to work on
making development versions of QEMU work with gcc4.
On 14 Mar 2008, at 10:53, Johannes Schindelin wrote:
WTF?
The point at which you start using profanity on a -
Hi,
Am 14.03.2008 um 11:53 schrieb Johannes Schindelin:
On Fri, 14 Mar 2008, Markus Hitter wrote:
Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
On Thu, 13 Mar 2008, Rick Vernam wrote:
[gcc4] Not supported? Okay, fine. But don't tell me it can't
work.
The fact of the matter is t
Hi,
On Fri, 14 Mar 2008, Markus Hitter wrote:
>
> Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
>
> >On Thu, 13 Mar 2008, Rick Vernam wrote:
> >
> > >[gcc4] Not supported? Okay, fine. But don't tell me it can't work.
> > >The fact of the matter is that I use it daily.
> > >
> > >Make c
Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
On Thu, 13 Mar 2008, Rick Vernam wrote:
[gcc4] Not supported? Okay, fine. But don't tell me it can't work.
The fact of the matter is that I use it daily.
Make configure fail horribly? Well, that seems a bit counter-
productive,
don't y
Hi,
On Thu, 13 Mar 2008, Rick Vernam wrote:
> [gcc4] Not supported? Okay, fine. But don't tell me it can't work.
> The fact of the matter is that I use it daily.
>
> Make configure fail horribly? Well, that seems a bit counter-productive,
> don't you think?
If you would only have research
On Thursday 13 March 2008 03:47:20 pm you wrote:
> > gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
>
> Which part of "gcc 4.x is not supported" didn't you understand?
>
> Paul
I understand every last bit of "gcc 4.x is not supported" ...
http://lists.gnu.org/archive/html/qemu-devel/2008-02/msg00011.html
On Thursday 13 March 2008 04:27:29 pm Ben Taylor wrote:
> On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <[EMAIL PROTECTED]> wrote:
> > > gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
> >
> > Which part of "gcc 4.x is not supported" didn't you understand?
> >
> > Paul
> >
> >
> > Apparently, we should make co
Hi,
On Thu, 13 Mar 2008, Ben Taylor wrote:
> On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <[EMAIL PROTECTED]> wrote:
>
> > > gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
> >
> > Which part of "gcc 4.x is not supported" didn't you understand?
>
> Apparently, we should make configure fail horribly if gcc4
On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <[EMAIL PROTECTED]> wrote:
> > gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
>
> Which part of "gcc 4.x is not supported" didn't you understand?
>
> Paul
>
>
> Apparently, we should make configure fail horribly if gcc4 is found even
if disable-gcc-check is enabl
> gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
Which part of "gcc 4.x is not supported" didn't you understand?
Paul
Pulling todays CVS (including Aurelien Jaron's recent commits), I've not been
able to build.
./configure --prefix=/usr --enable-ac97 --enable-alsa --disable-vnc-tls
--disable-linux-user --disable-gcc-check --target-list=i386-softmmu
make
[...]
gcc -Wall -O2 -g -fno-strict-aliasing -fno-reorde
> Could you try to find out which change in qemu triggers this behaviour?
> I don't have a windows to test, and given there weren't (yet :-) loud
> complaints I figure the problem might be connected to you local setup.
Ah, found it. I guess cvs after September requires updated .bin files.
Sorry.
Am Dienstag, den 02.01.2007, 23:48 -0800 schrieb Don Kitchen:
> I just compiled CVS and have experienced a regression with some windows
> qcow images (2000 pro and server). The images work with cvs I compiled back
> in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
>
> I
Don Kitchen wrote:
> I just compiled CVS and have experienced a regression with some windows
> qcow images (2000 pro and server). The images work with cvs I compiled back
> in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
Could you try to find out which change in qemu t
I just compiled CVS and have experienced a regression with some windows
qcow images (2000 pro and server). The images work with cvs I compiled back
in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
I'm running under linux, with only option -hda disk.
Thanks
_
Ozan Türkyılmaz wrote:
i have a request
cound you put cvs checkouts to another maling list ?
Since the number of commits per day is low, I prefer to have a single
mailing list.
Fabrice.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://li
Hi all,
Trying to download Qemu via CVS and keep getting:
cvs checkout: in directory .:
cvs [checkout aborted]: *PANIC* administration files missing
Any ideas ?
Dave.
___
Qemu-devel mailing list
Qemu-devel@nongnu.or
>"Oliver Gerlich"
> Hi,
> maybe it's the same problem as mentioned here:
> http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00077.html
>
> Could you try the patch given there?
That's it. Thanks.
I don't always get all of the mailing list messages. (Of course, it's
better than my ISP's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
maybe it's the same problem as mentioned here:
http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00077.html
Could you try the patch given there?
Good luck,
Oliver Gerlich
[EMAIL PROTECTED] wrote:
> I've been following the qemu-user's foru
I've been following the qemu-user's forum thread with CoMiKe describing how
to build qemu under windows with MingW. For those of us who don't use
Linux, the regular instructions are about as clear as mud.
CoMiKe's instructions are pretty good, and as soon as a few more people give
it a try and
On 5/29/05, Emmanuel Charpentier <[EMAIL PROTECTED]> wrote:
> So I decided to try the CVS version. The very same command line now
> gives me the Bios page telling that the image is not bootable.
>
> Reverting to the former version (0.7.0) still works fine. So I think
> this is a problem specific
Dear List,
I recently upgraded to QEMU 0.7.0 (self-compiled with kqemu on top of
Debian Sid). It worked fine, but I was unable to use the new 1152x960 an
1280x1024 graphics mode in most case, image seriously garbled, and
reverting to 640x480x8 in the remainder of cases ; 1024x768x16 is still
OK af
26 matches
Mail list logo
