http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33637
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-23 11:45:52 UTC --- Created attachment 22494 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22494 gcc46-pr33637.patch I guess the important question is, do we support (or even just pretend to support) configuring gcc (or binutils and other tools) in paths with spaces/tabs in pathnames? If not (it would surprise me if everything worked, e.g. $1=`cd $with_build_time_tools && pwd`/$2 in acx.m4 will not do what it expects if with_build_time_tools contains spaces in it), then I'd say this patch is the way to go. Otherwise, either we just shouldn't concatenate the extra arguments into NM_FOR_TARGET/AS_FOR_TARGET, but substitute into different vars and use them that way, or just special case trailing " -X32_64" and " -B -X32_64" in this script.
