From 434262ad518dad47841189b27fb9f3943d8206b8 Mon Sep 17 00:00:00 2001
From: Reid Spencer
Date: Fri, 9 Feb 2007 15:59:08 +0000
Subject: Remove references to gccld and gccas, adjusting the documentation to
mention llvm-ld and opt instead (if appropriate).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34094 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/FAQ.html | 25 +++++++++----------------
1 file changed, 9 insertions(+), 16 deletions(-)
(limited to 'docs/FAQ.html')
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
To work around this, perform the following steps:
-
- -
- Make sure the CC and CXX environment variables contains the full path to the
- LLVM GCC front end.
-
+ - Make sure the CC and CXX environment variables contains the full path to
+ the LLVM GCC front end.
- -
- Make sure that the regular C compiler is first in your PATH.
-
+ - Make sure that the regular C compiler is first in your PATH.
- -
- Add the string "-Wl,-native" to your CFLAGS environment variable.
-
+ - Add the string "-Wl,-native" to your CFLAGS environment variable.
-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.
-
+This will allow the llvm-ld 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.
--
cgit v1.1