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 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1629483 Title: Build fails on optionrom Status in QEMU: New Bug description: Git pseudo-bisected (focused on optionrom commits) it to this commit. commit cdbd727c20ad7aac7797dc8c95e485e1a4c6901b Author: Richard Henderson <r...@twiddle.net> 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. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1629483/+subscriptions
