Remove ltmain.in hack to recognize GCC -m* arguments

[Albert Chin]

Because libtool now passes through compiler arguments it doesn't
recognize, the code to pass through GCC's -m* arguments is not needed.

-- 
albert chin (address@hidden)

-- snip snip
2004-09-05  Albert Chin-A-Young  <address@hidden>

        * config/ltmain.in: Because we now pass through compiler
        arguments we doesn't recognize, the code to pass
        through GCC's -m* arguments is not needed.

Index: config/ltmain.in
===================================================================
RCS file: /cvsroot/libtool/libtool/config/ltmain.in,v
retrieving revision 1.16
diff -u -3 -p -r1.16 ltmain.in
--- config/ltmain.in    5 Sep 2004 18:10:03 -0000       1.16
+++ config/ltmain.in    5 Sep 2004 21:09:34 -0000
@@ -2804,29 +2804,6 @@ func_mode_link ()
        continue
        ;;
 
-      # gcc -m* arguments should be passed to the linker via $compiler_flags
-      # in order to pass architecture information to the linker
-      # (e.g. 32 vs 64-bit).  This may also be accomplished via -Wl,-mfoo
-      # but this is not reliable with gcc because gcc may use -mfoo to
-      # select a different linker, different libraries, etc, while
-      # -Wl,-mfoo simply passes -mfoo to the linker.
-      -m*)
-       # Unknown arguments in both finalize_command and compile_command need
-       # to be aesthetically quoted because they are evaled later.
-       arg=`$echo "X$arg" | $Xsed -e "$sed_quote_subst"`
-       case $arg in
-       *[\[\~\#\^\&\*\(\)\{\}\|\;\<\>\?\'\ \   ]*|*]*|"")
-         arg="\"$arg\""
-         ;;
-       esac
-       compile_command="$compile_command $arg"
-       finalize_command="$finalize_command $arg"
-       if test "$with_gcc" = "yes" ; then
-         compiler_flags="$compiler_flags $arg"
-       fi
-       continue
-       ;;
-
       -no-fast-install)
        fast_install=no
        continue