tests: don't always look for a C++ compiler named 'RCC'
authorStefano Lattarini <stefano.lattarini@gmail.com>
Tue, 1 Jan 2013 00:20:49 +0000 (01:20 +0100)
committerStefano Lattarini <stefano.lattarini@gmail.com>
Tue, 1 Jan 2013 00:20:49 +0000 (01:20 +0100)
commitf87ce5b01869361bb9f1035ae9f45bbf5e76b8bc
tree0789291516bd7ee983f4ce7bacc523ab9bcc48ef
parentf2443786a7dec55f498c06b8b207751aa06368cf
tests: don't always look for a C++ compiler named 'RCC'

On MacOS X (10.8), since the file system is case-insensitive, RCC
can point to the "Resource Compiler" of the Qt4 Toolkit:

    <http://doc.qt.digia.com/4.2/rcc.html>

That mismatch causes our configure script to erroneously think that
no working C++ compiler is present, and that is thus necessary to
skip all the test cases requiring such a compiler.

So only look for a compiler named 'RCC' if the file system is
case-sensible.

Issue spotted analyzing the testsuite logs reported in bug#13317.

* configure.ac: Adjust.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
configure.ac