diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index 6fb989a04d9..6513a9fdcac 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -231,9 +231,9 @@ libgcc.a library, which you can find by running These are the commands you need.

  % gmake
- % mkdir $CFEINSTALL/bytecode-libs
+ % mkdir $CFEINSTALL/lib
  % gmake -C runtime install-bytecode
- % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/bytecode-libs
+ % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/lib
 
  • Optionally, build a symbol table for the newly installed runtime diff --git a/docs/FAQ.html b/docs/FAQ.html index e43e3b22a57..9db6cc7d182 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -364,10 +364,10 @@ environment variable does not contain the libcrtend.a library. To fix it, verify that LLVM_LIB_SEARCH_PATH points to the correct directory and that libcrtend.a is inside. For pre-built LLVM GCC front ends, this should be the absolute path to -cfrontend/<platform>/llvm-gcc/bytecode-libs. If you've +cfrontend/<platform>/llvm-gcc/lib. If you've built your own LLVM GCC front end, then ensure that you've built and installed the libraries in llvm/runtime and have LLVM_LIB_SEARCH_PATH pointing -to the LLVMGCCDIR/bytecode-libs subdirectory. +to the $LLVMGCCDIR/lib subdirectory.

    @@ -460,7 +460,7 @@ find libcrtend.a.

    In order to find libcrtend.a, you must have the directory in which it lives in your LLVM_LIB_SEARCH_PATH environment variable. For the binary distribution of -the LLVM GCC front end, this will be the full path of the bytecode-libs +the LLVM GCC front end, this will be the full path of the lib directory inside of the LLVM GCC distribution.

    diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index ef561f6416a..e57defd27ca 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -548,7 +548,7 @@ You can set these on the command line, or better yet, set them in your .cshrc or .profile.
    -
    LLVM_LIB_SEARCH_PATH=LLVMGCCDIR/bytecode-libs +
    LLVM_LIB_SEARCH_PATH=LLVMGCCDIR/lib
    This environment variable helps the LLVM GCC front end find bytecode libraries that it will need for compilation. @@ -806,10 +806,10 @@ script to configure the build system:

    LLVM_LIB_SEARCH_PATH environment variable in your startup shell scripts. This environment variable is used to locate "system" libraries like "-lc" and "-lm" when linking. This variable should be set to -the absolute path of the bytecode-libs subdirectory of the GCC front -end, or LLVMGCCDIR/bytecode-libs. For example, one might set +the absolute path of the lib subdirectory of the GCC front +end, or LLVMGCCDIR/lib. For example, one might set LLVM_LIB_SEARCH_PATH to -/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs for the x86 +/home/vadve/lattner/local/x86/llvm-gcc/lib for the x86 version of the GCC front end on our research machines.

    diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index ca48bd46d24..1ebe0b54242 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -474,7 +474,7 @@ file. We usually run it from a crontab entry that looks ilke this:

    -5 3 * * *       LLVM_LIB_SEARCH_PATH=.../llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTRING... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
    +5 3 * * *       LLVM_LIB_SEARCH_PATH=.../llvm-gcc/lib $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTRING... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
     

    Or, you can create a shell script to encapsulate the running of the script. @@ -488,7 +488,7 @@ export WEBDIR=$BASE/testresults export LLVMGCCDIR=/proj/work/llvm/cfrontend/install export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH export LD_LIBRARY_PATH=/proj/install/lib -export LLVM_LIB_SEARCH_PATH=/proj/work/llvm/cfrontend/install/bytecode-libs +export LLVM_LIB_SEARCH_PATH=/proj/work/llvm/cfrontend/install/lib cd $BASE cp /proj/work/llvm/llvm/utils/NightlyTest.pl . nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals