configure: Handle having no c++ compiler in FORTIFY_SOURCE check
commite189091fba4481fa4c9d760f0bf9037620a51989
authorPeter Maydell <peter.maydell@linaro.org>
Mon, 26 Jun 2017 15:25:24 +0000 (26 16:25 +0100)
committerMichael Tokarev <mjt@tls.msk.ru>
Tue, 11 Jul 2017 08:18:37 +0000 (11 11:18 +0300)
tree6f0c11736662adef9f7e2522d9042dee37750864
parent667675623dc20b8d2f9ec2eff8a1c7eafcc86e19
configure: Handle having no c++ compiler in FORTIFY_SOURCE check

Our FORTIFY_SOURCE check assumes that $cxx refers to a working C++
compiler, with the result that if you don't happen to have one
then configure will spuriously print
  configure: line 4685: c++: command not found

Fix this by adding a 'has $cxx' check.

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
configure