lex and bison aren't needed to build llvm anymore.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@61560 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner
2009-01-02 07:10:51 +00:00
parent 0c7b39fb56
commit 01bb8b0c36
4 changed files with 2 additions and 31 deletions

View File

@@ -107,7 +107,7 @@
diff.</li> diff.</li>
<li>Patches should not include differences in generated code such as the <li>Patches should not include differences in generated code such as the
code generated by <tt>flex</tt>, <tt>bison</tt> or <tt>tblgen</tt>. The code generated by <tt>autoconf</tt> or <tt>tblgen</tt>. The
<tt>utils/mkpatch</tt> utility takes care of this for you.</li> <tt>utils/mkpatch</tt> utility takes care of this for you.</li>
</ol> </ol>

View File

@@ -307,11 +307,7 @@ up</a></li>
<li><a name="pf_3">No native code generation</a></li> <li><a name="pf_3">No native code generation</a></li>
<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li> <li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li> <li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
<li><a name="pf_6">The port is done using the MSYS shell.</a> <li><a name="pf_6">The port is done using the MSYS shell.</a></li>
<a href="http://www.mingw.org/MinGWiki/">Download</a> and install
bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source,
if necessary. Bison &amp; flex can be also grabbed from GNUWin32 sf.net
project.</li>
<li><a name="pf_7">Native code generation exists but is not complete.</a></li> <li><a name="pf_7">Native code generation exists but is not complete.</a></li>
<li><a name="pf_8">Binutils</a> up to post-2.17 has bug in bfd/cofflink.c <li><a name="pf_8">Binutils</a> up to post-2.17 has bug in bfd/cofflink.c
preventing LLVM from building correctly. Several workarounds have been preventing LLVM from building correctly. Several workarounds have been
@@ -375,18 +371,6 @@ href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
<td>For building the CFE</td> <td>For building the CFE</td>
</tr> </tr>
<tr>
<td><a href="http://www.gnu.org/software/flex">Flex</a></td>
<td>2.5.4</td>
<td>LEX compiler</td>
</tr>
<tr>
<td><a href="http://www.gnu.org/software/bison/bison.html">Bison</a></td>
<td>1.28, 1.35, 1.75, 1.875d, 2.0, or 2.1<br>(not 1.85 or 1.875)</td>
<td>YACC compiler</td>
</tr>
<tr> <tr>
<td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td> <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
<td>&ge;1.3</td> <td>&ge;1.3</td>

View File

@@ -198,11 +198,6 @@ changes are continually making the VS support better.</p>
<p>You will also need the <a href="http://www.cmake.org/">CMake</a> build <p>You will also need the <a href="http://www.cmake.org/">CMake</a> build
system since it generates the project files you will use to build with.</p> system since it generates the project files you will use to build with.</p>
<p>If you plan to modify any .y or .l files, you will need to have bison
and/or flex installed where Visual Studio can find them. Otherwise, you do
not need them and the pre-generated files that come with the source tree
will be used.</p>
<p> <p>
Do not install the LLVM directory tree into a path containing spaces (e.g. Do not install the LLVM directory tree into a path containing spaces (e.g.
C:\Documents and Settings\...) as the configure step will fail.</p> C:\Documents and Settings\...) as the configure step will fail.</p>

View File

@@ -781,8 +781,6 @@
<dl> <dl>
<dt><a name="AR"><tt>AR</tt></a> <small>(defaulted)</small></dt> <dt><a name="AR"><tt>AR</tt></a> <small>(defaulted)</small></dt>
<dd>Specifies the path to the <tt>ar</tt> tool.</dd> <dd>Specifies the path to the <tt>ar</tt> tool.</dd>
<dt><a name="BISON"><tt>BISON</tt></a><small>(configured)</small></dt>
<dd>Specifies the path to the <tt>bison</tt> tool.</dd>
<dt><a name="PROJ_OBJ_DIR"><tt>PROJ_OBJ_DIR</tt></a></dt> <dt><a name="PROJ_OBJ_DIR"><tt>PROJ_OBJ_DIR</tt></a></dt>
<dd>The directory into which the products of build rules will be placed. <dd>The directory into which the products of build rules will be placed.
This might be the same as This might be the same as
@@ -812,8 +810,6 @@
<dd>Provides the extension to be used on executables built by the makefiles. <dd>Provides the extension to be used on executables built by the makefiles.
The value may be empty on platforms that do not use file extensions for The value may be empty on platforms that do not use file extensions for
executables (e.g. Unix).</dd> executables (e.g. Unix).</dd>
<dt><a name="FLEX"><tt>FLEX</tt></a><small>(configured)</small></dt>
<dd>Specifies the path to the <tt>flex</tt> tool.</dd>
<dt><a name="INSTALL"><tt>INSTALL</tt></a><small>(configured)</small></dt> <dt><a name="INSTALL"><tt>INSTALL</tt></a><small>(configured)</small></dt>
<dd>Specifies the path to the <tt>install</tt> tool.</dd> <dd>Specifies the path to the <tt>install</tt> tool.</dd>
<dt><a name="LDFLAGS"><tt>LDFLAGS</tt></a><small>(configured)</small></dt> <dt><a name="LDFLAGS"><tt>LDFLAGS</tt></a><small>(configured)</small></dt>
@@ -981,8 +977,6 @@
INCFiles INCFiles
InternalTargets InternalTargets
LD.Flags LD.Flags
LexFiles
LexOutput
LibName.A LibName.A
LibName.BC LibName.BC
LibName.LA LibName.LA
@@ -1020,8 +1014,6 @@
ToolBuildPath ToolBuildPath
TopLevelTargets TopLevelTargets
UserTargets UserTargets
YaccFiles
YaccOutput
</tt></p> </tt></p>
</div> </div>