First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 141721
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Luca Barbato <lu_zero@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matthias Meißner <mtthsme@web.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 141721 depends on: Show dependency tree
Show dependency graph
Bug 141721 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-07-25 10:43 0000 
qemu-0.8.2 is out.

It compiles fine with the 0.8.1-ebuilds for -softmmu and -user.

When using custom cflags, both qemu-softmmu and qemu-user fail with
-march=athlon-xp, but compile with -mtune=athlon-xp, of course with gcc-3.*
only, no luck with gcc-4.1.1 yet

------- Comment #1 From Rémi Cardona 2006-07-28 08:01:52 0000 ------- 
compiled qemu-{softmmu,user} with gcc 4.1.1 and --as-needed on x86. Seems to
work fine. Haven't tried removing the unset CFLAGS though. Bump ok by me :)

Will try kqemu 1.3 when I get the chance.

------- Comment #2 From Carlo Marcelo Arenas Belon 2006-07-29 03:39:31 0000 ------- 
compiled with gcc-3.4.5 on amd64 and seems to work find while doing softmmu for
x86 and amd64 images.

gcc-4.1.1 will compile but segfault

------- Comment #3 From Matthias Meißner 2006-07-29 11:19:31 0000 ------- 
(In reply to comment #1)
> compiled qemu-{softmmu,user} with gcc 4.1.1 and --as-needed on x86. Seems to
> work fine. Haven't tried removing the unset CFLAGS though. Bump ok by me :)
> 
> Will try kqemu 1.3 when I get the chance.
> 

With me kqemu-1.3.0pre9 works fine here. qemu uses kqemu if the module is
loaded and i am in the group "qemu" of course.

I tried to compile qemu-softmmu-0.8.2 with gcc-4.1.1, but it failed, maybe i
can reproduce the error (some header could not be compiled, i use
linux-h.-2.6.17).

------- Comment #4 From Peter Read 2006-07-31 13:37:12 0000 ------- 
appears to compile cleanly on ~amd64, have yet to test properly though...

------- Comment #5 From Rémi Cardona 2006-07-31 23:50:56 0000 ------- 
hmm, seems that the tap interface for the network support is kind of flaky : it
creates an interface, but no name shows up in ifconfig (tap0 usually). Has
anyone seen this, can anyone confirm ?

------- Comment #6 From Chris Bainbridge (RETIRED) 2006-08-09 05:56:59 0000 ------- 
I can confirm 0.8.2 works and fixes the sticky mouse problem of 0.8.1.

------- Comment #7 From Nathan Sullivan 2006-08-10 17:46:50 0000 ------- 
Matthias, can you find out which header was failing? Ive been working with
plasmaroo lately trying to get linux-headers-2.6.17 ready for ~ on other archs,
so if theres a header issue id like to know about it :)

------- Comment #8 From Matthias Meißner 2006-08-13 05:52:28 0000 ------- 
About my reported header failure, it was an internal qemu header, not a
linux-header. linux-headers-2.6.17 are just fine on my PC (~x86).

It failed when being compiled with gcc-4.1.1 and CFLAGS="-Os ...", while it did
compile with gcc-4.1.1 and CFLAGS="-O2 ...".

qemu-user-0.8.2 and qemu-softmmu-0.8.2 both compiled fine with gcc-4.1.1 and
custom CFLAGS with gcc-4.1.1.

------- Comment #9 From Luca Barbato 2006-08-13 06:14:15 0000 ------- 
No, you need gcc-3 to build a correctly working qemu

------- Comment #10 From Luca Barbato 2006-08-17 00:16:19 0000 ------- 
I think is time to close this bug since qemu is in portage now
First Last Prev Next    No search results available      Search page      Enter new bug