+2004-09-06 Albert Chin-A-Young <china@thewrittenword.com>
+
+ Hopefully, passing unrecognised compiler arguments through
+ unmolested will prove to be a good plan for the 2.0 release. If
+ it goes awry, we can get back to where we were by reverting this
+ patch and the 2004-09-05 Albert Chin-A-Young patch, aka
+ gary@gnu.org--2004/libtool--devo--1.0--patch-169,172:
+
+ * config/ltmain.in (func_mode_link): Because we now pass through
+ compiler arguments we doesn't recognize, the code to pass
+ through GCC's -m* arguments is not needed.
+
2004-09-06 Albert Chin-A-Young <china@thewrittenword.com>
* Makefile.am (clean-ltmain-sh): Using '==' to test for equality
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