RPCSX/llvm
1
0
Fork 0
mirror of https://github.com/RPCSX/llvm.git synced 2024-11-28 14:10:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove most references to LLVM_LIB_SEARCH_PATH. It now only exists in the

Browse Source 
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
This commit is contained in:
Reid Spencer 2004-12-15 00:14:01 +00:00
parent 18d3b982b4
commit f96eb57a4b
4 changed files with 16 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/CFEBuildInstrs.html
View File

@ -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
</pre>
@ -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
</pre>
@ -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
</pre>
@ -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
</pre></li>
<li><p>Optionally, build a symbol table for the newly installed runtime

36
docs/FAQ.html
View File

@ -346,31 +346,6 @@ build.</p>
affects projects other than LLVM. Try upgrading or downgrading your GCC.</p>
</div>
<div class="question">
<p>
When I use the test suite, all of the C Backend tests fail. What is
wrong?
</p>
</div>
<div class="answer">
<p>
If you build LLVM and the C Backend tests fail in <tt>llvm/test/Programs</tt>,
then chances are good that the directory pointed to by the LLVM_LIB_SEARCH_PATH
environment variable does not contain the libcrtend.a library.
</p>
<p>
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
<tt>cfrontend/&lt;<i>platform</i>&gt;/llvm-gcc/lib</tt>. If you've
built your own LLVM GCC front end, then ensure that you've built and installed
the libraries in <tt>llvm/runtime</tt> and have LLVM_LIB_SEARCH_PATH pointing
to the <tt>$LLVMGCCDIR/lib</tt> subdirectory.
</p>
</div>
<div class="question">
<p>After CVS update, rebuilding gives the error "No rule to make target".</p>
</div>
@ -458,11 +433,12 @@ find libcrtend.a.
<div class="answer">
<p>
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 <tt>lib</tt>
directory inside of the LLVM GCC distribution.
</p>
The only way this can happen is if you haven't installed the runtime library. To
correct this, do:</p>
<pre>
% cd llvm/runtime
% make clean ; make install-bytecode
</pre>
</div>

30
docs/GettingStarted.html
View File

@ -185,7 +185,6 @@ and performance.
<li>Build the LLVM Suite:
<ol>
<li>Set your LLVM_LIB_SEARCH_PATH environment variable.</li>
<li><tt>gmake -k |&amp; tee gnumake.out
&nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
<li>If you get an "internal compiler error (ICE)" see <a href="#brokengcc">below</a>.</li>
@ -548,17 +547,16 @@ You can set these on the command line, or better yet, set them in your
<tt>.cshrc</tt> or <tt>.profile</tt>.
<dl>
<dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt><i>LLVMGCCDIR</i>/lib</tt>
<dd>
This environment variable helps the LLVM GCC front end find bytecode
libraries that it will need for compilation.
<p>
<dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
<dd>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.</dd>
<dt>alias llvmgcc <i>LLVMGCCDIR</i><tt>/bin/gcc</tt>
<dt>alias llvmg++ <i>LLVMGCCDIR</i><tt>/bin/g++</tt>
<dd>
These aliases allow you to use the LLVM C and C++ front ends without putting
them in your <tt>PATH</tt> or typing in their complete pathnames.
<dt>alias llvmgcc <i>LLVMGCCDIR</i><tt>/bin/gcc</tt></dt>
<dt>alias llvmg++ <i>LLVMGCCDIR</i><tt>/bin/g++</tt></dt>
<dd></dt>These aliases allow you to use the LLVM C and C++ front ends
without putting them in your <tt>PATH</tt> or typing in their complete
pathnames.</dd>
</dl>
</div>
@ -802,16 +800,6 @@ script to configure the build system:</p>
<p>
</ol>
<p>In addition to running <tt>configure</tt>, you must set the
<tt>LLVM_LIB_SEARCH_PATH</tt> environment variable in your startup shell
scripts. This environment variable is used to locate "system" libraries like
"<tt>-lc</tt>" and "<tt>-lm</tt>" when linking. This variable should be set to
the absolute path of the <tt>lib</tt> subdirectory of the GCC front
end, or <i>LLVMGCCDIR</i>/<tt>lib</tt>. For example, one might set
<tt>LLVM_LIB_SEARCH_PATH</tt> to
<tt>/home/vadve/lattner/local/x86/llvm-gcc/lib</tt> for the x86
version of the GCC front end on our research machines.</p>
</div>
<!-- ======================================================================= -->

3
docs/TestingGuide.html
View File

@ -474,7 +474,7 @@ file. We usually run it from a crontab entry that looks ilke this:
</p>
<pre>
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
</pre>
<p>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