effect of `-static'.
* ltmain.in: Do not create `.lo' objects when `-static' is
specified.
* NEWS: Updated.
+2003-10-07 Ralph Schleicher <rs@nunatak.allgaeu.org>
+
+ * doc/libtool.texi (Compile mode): Be more specific about the
+ effect of `-static'.
+ * ltmain.in: Do not create `.lo' objects when `-static' is
+ specified.
+ * NEWS: Updated.
+
2003-10-07 Gary V. Vaughan <gary@gnu.org>
* doc/libtool.texi (Invoking libtool): Updated.
NEWS - list of user-visible changes between releases of GNU Libtool
New in 1.5b: 2003-??-??; CVS version 1.5a, Libtool team:
+* Shared objects (.lo) are no longer created when `-static' is passed in
+ compile mode.
* libtoolize installs libtool.m4 (and ltdl.m4 if used) to AC_CONFIG_M4_DIR.
* Mode inferrence removed, shorthand for choosing modes added.
* Specifying -allow-undefined is now an error.
You can also pass compile specific flags using @samp{-Wc,@var{flag}}
and @samp{-Xcompiler @var{flag}}.
-If the @samp{-static} option is given, then a @samp{.o} file is built,
-even if libtool was configured with @samp{--disable-static}.
+If the @samp{-static} option is given, then only a @samp{.o} file is
+built, even if libtool was configured with @samp{--disable-static}.
Note that the @samp{-o} option is now fully supported. It is emulated
on the platforms that don't support it (by locking and moving the
;;
-static)
+ build_libtool_libs=no
build_old_libs=yes
continue
;;
fi
if test -n "$link_static_flag"; then
dlopen_self=$dlopen_self_static
+ # See comment for -static flag below, for more details.
+ compile_command="$compile_command $link_static_flag"
+ finalize_command="$finalize_command $link_static_flag"
fi
else
if test -z "$pic_flag" && test -n "$link_static_flag"; then
case $arg in
-all-static)
- if test -n "$link_static_flag"; then
- compile_command="$compile_command $link_static_flag"
- finalize_command="$finalize_command $link_static_flag"
- fi
+ # The effects of -all-static are defined in a previous loop.
continue
;;