[Qemu-devel] CVS build error

[Qemu-devel] CVS build error

[Rick Vernam]

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-reorder-blocks  -fno-gcse  -fno-tree-ch  -fno-optimize-sibling-calls  -fno-crossjumping  -fno-align-labels  -fno-align-jumps  -fno-align-functions   -mpreferred-stack-boundary=2 -fomit-frame-pointer  -m32 -I. -I.. -I/root/qemu/target-i386 -I/root/qemu -MMD -MP -DNEED_CPU_H -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/root/qemu/tcg -I/root/qemu/tcg/i386 -I/root/qemu/fpu -DHAS_AUDIO -DHAS_AUDIO_CHOICE -I/root/qemu/slirp -c -o 
op.o /root/qemu/target-i386/op.c
/root/qemu/target-i386/ops_template_mem.h: In function 'op_cmpxchgb_kernel_T0_T1_EAX_cc':
../softmmu_header.h:170: error: can't find a register in class 'Q_REGS' while reloading 'asm'
make[1]: *** [op.o] Error 1
make[1]: Leaving directory `/root/qemu/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2


gcc --version
gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)

system is 32-bit i686

Is this on my end, or just the current state of things?

thanks
-Rick

Re: [Qemu-devel] CVS build error

[Paul Brook]

> 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

Re: [Qemu-devel] CVS build error

[Ben Taylor]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <paul@codesourcery.com> 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 enabled.

[-- Attachment #2: Type: text/html, Size: 635 bytes --]

Re: [Qemu-devel] CVS build error

[Johannes Schindelin]

Hi,

On Thu, 13 Mar 2008, Ben Taylor wrote:

> On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <paul@codesourcery.com> 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 is found even 
> if disable-gcc-check is enabled.

No, we should educate people so we do not have to clutter our source code 
with unnecessary messages.

I mean, it says what it should say, really.  Really.

Hth,
Dscho

Re: [Qemu-devel] CVS build error

[Rick Vernam]

On Thursday 13 March 2008 04:27:29 pm Ben Taylor wrote:
> On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <paul@codesourcery.com> 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 enabled.

It's quite interesting - the arrogant and presumptuous assertions that are 
made.

On a different system (x86_64) - my everyday-use laptop, actually - I have 
only gcc 4.1.2.
If you're familiar with Gentoo, you'll know what this means:
gcc-config -l
 [1] x86_64-pc-linux-gnu-4.1.2 *


On this laptop, I run qemu cvs, configured as such:
./configure --prefix=/usr --enable-ac97 --enable-alsa --disable-vnc-tls --disable-linux-user --disable-gcc-check --target-list=x86_64-softmmu

and build with no problems.  I run it every single day.  in fact, it is 
running right now.  It runs ms and linux guests without problem.


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?

Re: [Qemu-devel] CVS build error

[Rick Vernam]

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

not supported, but clearly being addressed.
hence my question: or just the current state of things?

I missed this
http://lists.gnu.org/archive/html/qemu-devel/2008-02/msg00026.html
while looking prior to posting.  that answers my question.

Thanks, Paul, for the 'helpful' response - for without it, I would not have 
dug deeper to find my answer.  :-)

Re: [Qemu-devel] CVS build error

[Johannes Schindelin]

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 researched a _little_ bit, you would have found out 
that x86, by far the most common platform at the moment, which you should 
have known before stating what you stated, does _not_ work with gcc4.

So all you said is just bull.

Ciao,
Dscho

Re: [Qemu-devel] CVS build error

[Markus Hitter]

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 you think?
>
> If you would only have researched a _little_ bit, you would have  
> found out
> that x86, by far the most common platform at the moment, which you  
> should
> have known before stating what you stated, does _not_ work with gcc4.

OK, so Rick is guilty not using the most common platform. Wasn't it  
one of the major goals of qemu to work on a wide variety of different  
platforms?


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/

Re: [Qemu-devel] CVS build error

[Johannes Schindelin]

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 configure fail horribly?  Well, that seems a bit 
> > >counter-productive, don't you think?
> >
> >If you would only have researched a _little_ bit, you would have found 
> >out that x86, by far the most common platform at the moment, which you 
> >should have known before stating what you stated, does _not_ work with 
> >gcc4.
> 
> OK, so Rick is guilty not using the most common platform. Wasn't it one 
> of the major goals of qemu to work on a wide variety of different 
> platforms?

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 was against removing this safety valve, because it does _nothing_ to 
help users understand why QEmu does not compile.

The situation now: gcc4 is not supported, but might work. configure tells 
you as much, and even gives you rope to try nevertheless.

The situation suggested: configure silently ignores the fact that gcc4 is 
the current compiler, and in some (not at all rare) cases, the compilation 
just fails without a clue.

So I absolutely _fail_ to understand what you thought, implying that I was 
restricting platform variability.

Sheesh,
Dscho

Re: [Qemu-devel] CVS build error

[Andreas Färber]

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 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 researched a _little_ bit, you would have  
>>> found
>>> out that x86, by far the most common platform at the moment, which  
>>> you
>>> should have known before stating what you stated, does _not_ work  
>>> with
>>> gcc4.
>>
>> OK, so Rick is guilty not using the most common platform. Wasn't it  
>> one
>> of the major goals of qemu to work on a wide variety of different
>> platforms?
>
> 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 was against removing this safety valve, because it does _nothing_ to
> help users understand why QEmu does not compile.
>
> The situation now: gcc4 is not supported, but might work. configure  
> tells
> you as much, and even gives you rope to try nevertheless.
>
> The situation suggested: configure silently ignores the fact that  
> gcc4 is
> the current compiler, and in some (not at all rare) cases, the  
> compilation
> just fails without a clue.

The situation suggested 2: configure always fails for gcc4, cutting  
said rope

> 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: In your own quote, he  
opposes the proposal to "make configure fail horribly". ;-)

Cheers,
Andreas

Re: [Qemu-devel] CVS build error

[Philip Boulain]

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 -devel list is the  
point at which you need to put the keyboard down and come back later.

> 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.

No, by the looks of it, he was refuting Ben's suggestion that it should:

Ben/Rick:
>> Apparently, we should make configure fail horribly if gcc4 is  
>> found even

>> if disable-gcc-check is enabled.
> Make configure fail horribly?  Well, that seems a bit counter- 
> productive,

> don't you think?

-- 
| Philip Boulain   PhD student | #!bash |   "After all, dumbing down   |
| IAM, ECS, Uni of Southampton | :(){:| | Xanadu sure  worked well for |
| http://zepler.net/~lionsphil | :&};:# | Tim Berners-Lee!"-Ted Nelson |

Re: [Qemu-devel] CVS build error

[Rick Vernam]

> 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 removing this safety valve, because it does _nothing_ to
> help users understand why QEmu does not compile.
>
> The situation now: gcc4 is not supported, but might work. configure tells
> you as much, and even gives you rope to try nevertheless.
but if you're not sure of the current state and you want to find out - do not 
ask.  such questions are not taken nicely.

>
> The situation suggested: configure silently ignores the fact that gcc4 is
> the current compiler, and in some (not at all rare) cases, the compilation
> just fails without a clue.
I don't know who's post you've read.  Mine was essentialy this: "Is this on my 
end, or just the current state of things?"
Please, forgive me for knowing only that it works sometimes and not others.

>
> So I absolutely _fail_ to understand what you thought, implying that I was
> restricting platform variability.
>
> Sheesh,
> Dscho

Re: [Qemu-devel] CVS build error

[Rick Vernam]

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: In your own quote, he  
> opposes the proposal to "make configure fail horribly". ;-)

okay, good, so it's not just me :-)
And it is necessary to have configure require a special step to build with 
gcc4 anyway.

I never suggested changing anything.  just trying to learn a thing or two 
here.

Sheesh is right, indeed.

Re: [Qemu-devel] CVS build error

[Rick Vernam]

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...

Re: [Qemu-devel] CVS build error

[Thiemo Seufer]

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 of the target support to TCG would be
more productive than this whole discussion.


Thiemo