This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/38546] configure: too many arguments
- From: "rwild at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Dec 2008 17:02:37 -0000
- Subject: [Bug bootstrap/38546] configure: too many arguments
- References: <bug-38546-10263@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #1 from rwild at gcc dot gnu dot org 2008-12-19 17:02 -------
The code in question is
if test -f $gcc_cv_binutils_srcdir/configure.in \
&& test -f ../binutils/Makefile \
&& test x$build = x$host; then
gcc_cv_nm=../binutils/nm-new$build_exeext
elif test -x nm$build_exeext; then
gcc_cv_nm=./nm$build_exeext
elif test -x $NM_FOR_TARGET; then
gcc_cv_nm="$NM_FOR_TARGET"
else
...
and the line in question is the one containing
test -x $NM_FOR_TARGET
This idiom exists in current trunk as well, so presumably also the bug,
and also in a couple of other places in this file.
I'm not sure whether NM_FOR_TARGET is required here to be one word only,
but that would seem like a bug itself to me.
--
rwild at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rwild at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38546