maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Clean up docs references to './configure' in preparation for deprecating in-source builds 

http://reviews.llvm.org/D8787

llvm-svn: 236144
This commit is contained in:
Jonathan Roelofs 2015-04-29 20:06:41 +00:00
parent 0e20822887
commit cf1ba1d8c0
5 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
llvm/autoconf/configure.ac
View File

@ -105,7 +105,7 @@ if test "$CXX" = "clang++" ; then
], ],
[ [
AC_MSG_RESULT([no]) AC_MSG_RESULT([no])
AC_MSG_ERROR([Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler ./configure ...]) AC_MSG_ERROR([Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler LLVM_SRC_DIR/configure ...])
]) ])
AC_LANG_POP([C++]) AC_LANG_POP([C++])
fi fi

4
llvm/configure vendored
View File

@ -3605,8 +3605,8 @@ sed 's/^/| /' conftest.$ac_ext >&5
{ echo "$as_me:$LINENO: result: no" >&5 { echo "$as_me:$LINENO: result: no" >&5
echo "${ECHO_T}no" >&6; } echo "${ECHO_T}no" >&6; }
{ { echo "$as_me:$LINENO: error: Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler ./configure ..." >&5 { { echo "$as_me:$LINENO: error: Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler LLVM_SRC_DIR/configure ..." >&5
echo "$as_me: error: Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler ./configure ..." >&2;} echo "$as_me: error: Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler LLVM_SRC_DIR/configure ..." >&2;}
{ (exit 1); exit 1; }; } { (exit 1); exit 1; }; }
fi fi

10
llvm/docs/BuildingLLVMWithAutotools.rst
View File

@ -121,7 +121,7 @@ To configure LLVM, follow these steps:
.. code-block:: console .. code-block:: console
% SRC_ROOT/configure --prefix=/install/path [other options] % $LLVM_SRC_DIR/configure --prefix=/install/path [other options]
Compiling the LLVM Suite Source Code Compiling the LLVM Suite Source Code
------------------------------------ ------------------------------------
@ -187,7 +187,7 @@ source code:
``gmake install`` ``gmake install``
Installs LLVM header files, libraries, tools, and documentation in a hierarchy Installs LLVM header files, libraries, tools, and documentation in a hierarchy
under ``$PREFIX``, specified with ``./configure --prefix=[dir]``, which under ``$PREFIX``, specified with ``$LLVM_SRC_DIR/configure --prefix=[dir]``, which
defaults to ``/usr/local``. defaults to ``/usr/local``.
``gmake -C runtime install-bytecode`` ``gmake -C runtime install-bytecode``
@ -240,7 +240,7 @@ There are some HTML documents that have not yet been converted to the new
system (which uses the easy-to-read and easy-to-write system (which uses the easy-to-read and easy-to-write
`reStructuredText <http://sphinx-doc.org/rest.html>`_ plaintext markup `reStructuredText <http://sphinx-doc.org/rest.html>`_ plaintext markup
language). language).
The generated documentation is built in the ``SRC_ROOT/docs`` directory using The generated documentation is built in the ``$LLVM_SRC_DIR/docs`` directory using
a special makefile. a special makefile.
For instructions on how to install Sphinx, see For instructions on how to install Sphinx, see
`Sphinx Introduction for LLVM Developers `Sphinx Introduction for LLVM Developers
@ -250,7 +250,7 @@ HTML documentation by doing the following:
.. code-block:: console .. code-block:: console
$ cd SRC_ROOT/docs $ cd $LLVM_SRC_DIR/docs
$ make -f Makefile.sphinx $ make -f Makefile.sphinx
This creates a ``_build/html`` sub-directory with all of the HTML files, not This creates a ``_build/html`` sub-directory with all of the HTML files, not
@ -296,7 +296,7 @@ This is accomplished in the typical autoconf manner:
.. code-block:: console .. code-block:: console
% SRC_ROOT/configure % $LLVM_SRC_DIR/configure
The LLVM build will place files underneath *OBJ_ROOT* in directories named after The LLVM build will place files underneath *OBJ_ROOT* in directories named after
the build type: the build type:

2
llvm/docs/FAQ.rst
View File

@ -102,7 +102,7 @@ grabbing the wrong linker/assembler/etc, there are two ways to fix it:
.. code-block:: console .. code-block:: console
% PATH=[the path without the bad program] ./configure ... % PATH=[the path without the bad program] $LLVM_SRC_DIR/configure ...
This is still somewhat inconvenient, but it allows ``configure`` to do its This is still somewhat inconvenient, but it allows ``configure`` to do its
work without having to adjust your ``PATH`` permanently. work without having to adjust your ``PATH`` permanently.

2
llvm/docs/HowToBuildOnARM.rst
View File

@ -40,7 +40,7 @@ on the ARMv6 and ARMv7 architectures and may be inapplicable to older chips.
.. code-block:: bash .. code-block:: bash
./configure --build=armv7l-unknown-linux-gnueabihf \ ../$LLVM_SRC_DIR/configure --build=armv7l-unknown-linux-gnueabihf \
--host=armv7l-unknown-linux-gnueabihf \ --host=armv7l-unknown-linux-gnueabihf \
--target=armv7l-unknown-linux-gnueabihf --with-cpu=cortex-a9 \ --target=armv7l-unknown-linux-gnueabihf --with-cpu=cortex-a9 \
--with-float=hard --with-abi=aapcs-vfp --with-fpu=neon \ --with-float=hard --with-abi=aapcs-vfp --with-fpu=neon \