Commit d869a8c4 by Nathanael Nerode

configure.in: Clarify comments.

2003-03-28  Nathanael Nerode  <neroden@gcc.gnu.org>

	* configure.in: Clarify comments.
	* configure: Regenerate.

From-SVN: r64990
parent 84dfe365
2003-03-28 Nathanael Nerode <neroden@gcc.gnu.org>
* configure.in: Clarify comments.
* configure: Regenerate.
2003-03-28 Ulrich Weigand <uweigand@de.ibm.com>
* config/s390/s390.md ("literal_pool_31"): Output pool anchor
......
......@@ -1448,7 +1448,13 @@ if test -f ../ld/Makefile; then
rm -f collect-ld; $symbolic_link ../ld/ld-new$host_exeext collect-ld$host_exeext 2>/dev/null
fi
# Figure out what assembler we will be using.
# Identify the assembler which will work hand-in-glove with the newly
# built GCC, so that we can examine its features. This is the assembler
# which will be driven by the driver program.
#
# If build != host, and we aren't building gas in-tree, we identify a
# build->target assembler and hope that it will have the same features
# as the host->target assembler we'll be using.
AC_MSG_CHECKING(what assembler to use)
in_tree_gas=no
gcc_cv_as=
......@@ -1537,7 +1543,13 @@ case $in_tree_gas in
;;
esac
# Figure out what linker we will be using.
# Identify the linker which will work hand-in-glove with the newly
# built GCC, so that we can examine its features. This is the linker
# which will be driven by the driver program.
#
# If build != host, and we aren't building gas in-tree, we identify a
# build->target linker and hope that it will have the same features
# as the host->target linker we'll be using.
AC_MSG_CHECKING(what linker to use)
in_tree_ld=no
gcc_cv_ld=
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment