summaryrefslogtreecommitdiff
path: root/dragonegg/test/dragonegg-lit.site.cfg.in
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2013-02-23 17:26:41 +0000
committerDuncan Sands <baldrick@free.fr>2013-02-23 17:26:41 +0000
commit9b627b1e9ffc01f0125b308781a99cf340747873 (patch)
treee6674c6fe8394e0580190101bf69c9895739fa3c /dragonegg/test/dragonegg-lit.site.cfg.in
parentad81f48dfb79e56600a89d37e68406d441384748 (diff)
Rather than basing the list of supported languages on how gcc was configured,
instead try to compile a mini program for each language. The problem with looking at the configure line is that: - It can contain logical expressions like "all"; - Default languages (C) might not be listed; - Distributions generally configure gcc with all languages, but the actual front-end is not installed by default (you have to install an extra package to get it). For example on Debian based systems gcc will always have been configured for Fortran yet you can't compile Fortran programs unless you install the gfortran package.
Diffstat (limited to 'dragonegg/test/dragonegg-lit.site.cfg.in')
-rw-r--r--dragonegg/test/dragonegg-lit.site.cfg.in1
1 files changed, 0 insertions, 1 deletions
diff --git a/dragonegg/test/dragonegg-lit.site.cfg.in b/dragonegg/test/dragonegg-lit.site.cfg.in
index 0de76e22c1f..0fddfbf66dc 100644
--- a/dragonegg/test/dragonegg-lit.site.cfg.in
+++ b/dragonegg/test/dragonegg-lit.site.cfg.in
@@ -1,6 +1,5 @@
config.dragonegg_plugin = "@DRAGONEGG_PLUGIN@"
config.gcc_executable = "@GCC@"
-config.gcc_languages = "@GCC_LANGUAGES@"
config.llvm_tools_dir = "@LLVM_TOOLS_DIR@"
config.target_triple = "@TARGET_TRIPLE@"
config.test_output_dir = "@TEST_OUTPUT_DIR@"