diff options
author | Michael Roth <mdroth@linux.vnet.ibm.com> | 2019-03-15 20:24:30 -0500 |
---|---|---|
committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2019-03-18 10:24:20 -0500 |
commit | 40cebc58117dbc6275a5d7c4e3ba6611964d9e6e (patch) | |
tree | 64dc75e72adc08ca96ab2d582c65ba036a03e6ad /hmp.c | |
parent | 82a58d270c6fbbe2f2381224946340fd3814a273 (diff) | |
download | qemu-40cebc58117dbc6275a5d7c4e3ba6611964d9e6e.zip qemu-40cebc58117dbc6275a5d7c4e3ba6611964d9e6e.tar.gz qemu-40cebc58117dbc6275a5d7c4e3ba6611964d9e6e.tar.bz2 |
qga-win: fix VSS build breakage due to unintended gnu99 C++ flag
Commit 7be41675f7c set -std=gnu99 for C code via QEMU_CFLAGS. Currently
we generate a "custom" QEMU_CXXFLAGS for VSS DLL C++ build by
filtering out some options from QEMU_CFLAGS and adding some others.
Since we don't filter out -std=gnu99 currently this breaks builds when
VSS support is enabled.
We could keep the existing approach, filter out -std=gnu99 from
QEMU_CFLAGS, and add -std=gnu++98, like configure currently does for
QEMU_CXXFLAGS, but as it turns out our resulting QEMU_CXXFLAGS would
be exactly what configure already generates, just with these filtered
out:
-fstack-protector-all -fstack-protector-strong
and these added:
-Wno-unknown-pragmas -Wno-delete-non-virtual-dtor
So fix the issue by re-using configure-generated QEMU_CXXFLAGS and
just handling these specific changes.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'hmp.c')
0 files changed, 0 insertions, 0 deletions