aboutsummaryrefslogtreecommitdiffstats
path: root/docs/FAQ.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/FAQ.html')
-rw-r--r--docs/FAQ.html25
1 files changed, 9 insertions, 16 deletions
diff --git a/docs/FAQ.html b/docs/FAQ.html
index 2dffd20..d540edd 100644
--- a/docs/FAQ.html
+++ b/docs/FAQ.html
@@ -460,28 +460,21 @@ or translation to the C back end). That is why configure thinks your system
<p>
To work around this, perform the following steps:
</p>
-
<ol>
- <li>
- Make sure the CC and CXX environment variables contains the full path to the
- LLVM GCC front end.
- </li>
+ <li>Make sure the CC and CXX environment variables contains the full path to
+ the LLVM GCC front end.</li>
- <li>
- Make sure that the regular C compiler is first in your PATH.
- </li>
+ <li>Make sure that the regular C compiler is first in your PATH. </li>
- <li>
- Add the string "-Wl,-native" to your CFLAGS environment variable.
- </li>
+ <li>Add the string "-Wl,-native" to your CFLAGS environment variable.</li>
</ol>
<p>
-This will allow the gccld linker to create a native code executable instead of
-a shell script that runs the JIT. Creating native code requires standard
-linkage, which in turn will allow the configure script to find out if code is
-not linking on your system because the feature isn't available on your system.
-</p>
+This will allow the <tt>llvm-ld</tt> linker to create a native code executable
+instead of shell script that runs the JIT. Creating native code requires
+standard linkage, which in turn will allow the configure script to find out if
+code is not linking on your system because the feature isn't available on your
+system.</p>
</div>
<div class="question">