aboutsummaryrefslogtreecommitdiff
path: root/gitdm.config
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2019-12-11 15:34:27 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2020-01-24 20:59:17 +0100
commitdb5adeaa84d0d70dabd41500e72493fec04408ac (patch)
tree04cfa7125085524f3443fdebba2f911f4d6c9a62 /gitdm.config
parent673b0add9ea7f432f34c1c99eaa7c567012fc838 (diff)
downloadqemu-db5adeaa84d0d70dabd41500e72493fec04408ac.zip
qemu-db5adeaa84d0d70dabd41500e72493fec04408ac.tar.gz
qemu-db5adeaa84d0d70dabd41500e72493fec04408ac.tar.bz2
build-sys: clean up flags included in the linker command line
Some of the CFLAGS that are discovered during configure, for example compiler warnings, are being included on the linker command line because QEMU_CFLAGS is added to it. Other flags, such as the -m32, appear twice because they are included in both QEMU_CFLAGS and LDFLAGS. All this leads to confusion with respect to what goes in which Makefile variables (and we have plenty). So, introduce QEMU_LDFLAGS for flags discovered by configure, following the lead of QEMU_CFLAGS, and stop adding to it: 1) options that are already in CFLAGS, for example "-g" 2) duplicate options At the same time, options that _are_ needed by both compiler and linker must now be added to both QEMU_CFLAGS and QEMU_LDFLAGS, which is clearer. This is mostly -fsanitize options. For now, --extra-cflags has this behavior (but --extra-cxxflags does not). Meson will not include CFLAGS on the linker command line, do the same in our build system as well. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'gitdm.config')
0 files changed, 0 insertions, 0 deletions