From f96eb57a4bb9ceca22fa9609cc6eca8f74fa565e Mon Sep 17 00:00:00 2001 From: Reid Spencer Date: Wed, 15 Dec 2004 00:14:01 +0000 Subject: [PATCH] Remove most references to LLVM_LIB_SEARCH_PATH. It now only exists in the GettingStarted.html document in the environment section and only as an optional feature. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@18944 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CFEBuildInstrs.html | 7 ------- docs/FAQ.html | 36 ++++++------------------------------ docs/GettingStarted.html | 32 ++++++++++---------------------- docs/TestingGuide.html | 3 +-- 4 files changed, 17 insertions(+), 61 deletions(-) diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index 6513a9fdcac..68541ed2830 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -132,8 +132,6 @@ invalid code. Instead, use the system assembler and linker. % cd build % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ --disable-shared --enable-languages=c,c++ - % gmake - % setenv LLVM_LIB_SEARCH_PATH `pwd`/gcc % gmake all; gmake install @@ -143,8 +141,6 @@ invalid code. Instead, use the system assembler and linker. % cd build % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ --disable-shared --enable-languages=c,c++ --disable-c-mbchar - % gmake - % setenv LLVM_LIB_SEARCH_PATH `pwd`/gcc % gmake all; gmake install @@ -163,8 +159,6 @@ functions from C as referenced from C++, so we typically configure with % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ --disable-shared --enable-languages=c,c++ --host=sparcv9-sun-solaris2.8 \ --disable-c-mbchar - % gmake - % setenv LLVM_LIB_SEARCH_PATH `pwd`/gcc % gmake all; gmake install @@ -233,7 +227,6 @@ libgcc.a library, which you can find by running % gmake % mkdir $CFEINSTALL/lib % gmake -C runtime install-bytecode - % 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 9db6cc7d182..9359324019a 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -346,31 +346,6 @@ build.

    affects projects other than LLVM. Try upgrading or downgrading your GCC.

    -
    -

    -When I use the test suite, all of the C Backend tests fail. What is -wrong? -

    -
    - -
    -

    -If you build LLVM and the C Backend tests fail in llvm/test/Programs, -then chances are good that the directory pointed to by the LLVM_LIB_SEARCH_PATH -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/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/lib subdirectory. -

    -
    -

    After CVS update, rebuilding gives the error "No rule to make target".

    @@ -458,11 +433,12 @@ 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 lib -directory inside of the LLVM GCC distribution. -

    +The only way this can happen is if you haven't installed the runtime library. To +correct this, do:

    +
    +  % cd llvm/runtime
+  % make clean ; make install-bytecode
+
    diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index e57defd27ca..cb81b19c3f8 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -185,7 +185,6 @@ and performance.
  • Build the LLVM Suite:
      -
    1. Set your LLVM_LIB_SEARCH_PATH environment variable.
    2. gmake -k |& tee gnumake.out    # this is csh or tcsh syntax
    3. If you get an "internal compiler error (ICE)" see below.
      4. @@ -548,17 +547,16 @@ You can set these on the command line, or better yet, set them in your .cshrc or .profile.
      -
      LLVM_LIB_SEARCH_PATH=LLVMGCCDIR/lib -
      - This environment variable helps the LLVM GCC front end find bytecode - libraries that it will need for compilation. -

      - -

      alias llvmgcc LLVMGCCDIR/bin/gcc -
      alias llvmg++ LLVMGCCDIR/bin/g++ -
      - These aliases allow you to use the LLVM C and C++ front ends without putting - them in your PATH or typing in their complete pathnames. +
      LLVM_LIB_SEARCH_PATH=/path/to/your/bytecode/libs
      +
      This environment variable helps LLVM linking tools find the locations + of your bytecode libraries. It is optional and provided only a convenience + since you can specify the paths using the -L options of the tools.
      + +
      alias llvmgcc LLVMGCCDIR/bin/gcc
      +
      alias llvmg++ LLVMGCCDIR/bin/g++
      +
      These aliases allow you to use the LLVM C and C++ front ends + without putting them in your PATH or typing in their complete + pathnames.
      @@ -802,16 +800,6 @@ script to configure the build system:

    -

    In addition to running configure, you must set the -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 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/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 1ebe0b54242..5979d3ec8a2 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/lib $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTRING... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
+5 3 * * *  $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTORY... $HOME/buildtest-X86 $HOME/cvs/testresults-X86

    Or, you can create a shell script to encapsulate the running of the script. @@ -488,7 +488,6 @@ 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/lib cd $BASE cp /proj/work/llvm/llvm/utils/NightlyTest.pl . nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals -- 2.34.1