semantic: 0.190
PID: 0.107
other: 0.098
boot: 0.095
device: 0.095
network: 0.080
debug: 0.064
graphic: 0.058
vnc: 0.042
files: 0.041
KVM: 0.038
socket: 0.034
performance: 0.030
permissions: 0.027
debug: 0.412
boot: 0.119
files: 0.096
other: 0.069
PID: 0.052
device: 0.044
performance: 0.037
socket: 0.036
semantic: 0.033
vnc: 0.027
KVM: 0.025
network: 0.021
graphic: 0.015
permissions: 0.015

Build fails on optionrom

Git pseudo-bisected (focused on optionrom commits) it to this commit.

commit cdbd727c20ad7aac7797dc8c95e485e1a4c6901b
Author: Richard Henderson <email address hidden>
Date:   Thu Jul 7 21:49:36 2016 -0700

    build: Use $(AS) for optionrom explicitly


Build output (non-verbose):

  AS    optionrom/linuxboot.o
cpp: fatal error: '-c' is not a valid option to the preprocessor
compilation terminated.
cpp: fatal error: '-c' is not a valid option to the preprocessor
compilation terminated.
  CC    optionrom/linuxboot_dma.o
  CC    /home/bkamath/dev/workspace/block-2/mothra/output/sp0/targetqga/main.o
  AS    optionrom/kvmvapic.o
cpp: fatal error: '-c' is not a valid option to the preprocessor
compilation terminated.

Steps to reproduce:
Using buildroot and overriding qemu version to 2.7.0
Fedora 24, cpp (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)

I tried first just building without the -c option but it hangs indefinitely. Reverting the above listed commit fixes the problem on my platform. I didn't dive much further into this, because this seems like a regression.

I am seeing the same problem.  Cross compiling QEMU 2.7 using buildroot get fatal error -c is not a valid option.  As Benjamin states removing the -c flag from Makefile gets through the compile, but when booting a virtual image of Ubuntu 16.04 the network does not come up (console is live and you can login through the console, but the only network interface is loopback) I have not diagnosed further.

I was not able to simply back out the optionrom commit Benjamin cites... caused problems elsewhere, perhaps because I was not doing it right.  Reverting to QEMU 2.6.2 does work.

David

Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

[Expired for QEMU because there has been no activity for 60 days.]