Cheers,
Ralf
* doc/libtool.texi (Implementation issues): Note that both
prefix and suffix of a library may differ.
(Using libtool, Creating object files, Linking libraries):
Remove last documentation traces of the age when `foo.lo' was
the PIC object file and not the `libtool object' text file.
(libtool script contents) <compiler_o_lo>: Remove description
of this variable. It was removed from libtool in 1.5 times.
Index: doc/libtool.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.209
diff -u -r1.209 libtool.texi
--- doc/libtool.texi 30 Jan 2006 20:24:37 -0000 1.209
+++ doc/libtool.texi 14 Feb 2006 22:50:04 -0000
@@ -322,9 +322,10 @@
a consistent way.
@item
-It is not always obvious with what suffix a shared library should be
-installed. This makes it difficult for @file{Makefile} rules, since they
-generally assume that file names are the same from host to host.
+It is not always obvious with what prefix or suffix a shared library
+should be installed. This makes it difficult for @file{Makefile} rules,
+since they generally assume that file names are the same from host to
+host.
@item
The system needs a simple library version number abstraction, so that
@@ -439,8 +440,8 @@
function, which is usually found in the standalone math library, and not
the C library (@pxref{Trig Functions, , Trigonometric Functions, libc,
The GNU C Library Reference Manual}). So, we need to add @option{-lm} to
-the end of the link line whenever we link @file{foo.o} or @file{foo.lo}
-into an executable or a library (@pxref{Inter-library dependencies}).
+the end of the link line whenever we link @file{foo.lo} into an
+executable or a library (@pxref{Inter-library dependencies}).
The same rule applies whenever you use functions that don't appear in
the standard C address@hidden you need to add the appropriate
@@ -473,8 +474,8 @@
burger$
@end example
-The above compiler command produces an object file, @file{main.o}, from
-the source file @file{main.c}.
+The above compiler command produces an object file, usually named
address@hidden, from the source file @file{main.c}.
For most library systems, creating object files that become part of a
static library is as simple as creating object files that are linked to
@@ -665,7 +666,7 @@
burger$ @kbd{libtool --mode=link gcc -g -O -o libhello.la foo.lo hello.lo \
-rpath /usr/local/lib -lm}
rm -fr @value{objdir}/libhello.a @value{objdir}/libhello.la
-ld -Bshareable -o @value{objdir}/libhello.so.0.0 foo.lo hello.lo -lm
+ld -Bshareable -o @value{objdir}/libhello.so.0.0 @value{objdir}/foo.o
@value{objdir}/hello.o -lm
ar cru @value{objdir}/libhello.a foo.o hello.o
ranlib @value{objdir}/libhello.a
creating libhello.la
@@ -5228,12 +5229,6 @@
simultaneously. Set to @samp{yes} or @samp{no}.
@end defvar
address@hidden compiler_o_lo
-Whether the compiler supports compiling directly to a @samp{.lo} file,
-i.e.@: whether object files do not have to have the suffix @samp{.o}.
-Set to @samp{yes} or @samp{no}.
address@hidden defvar
-
@defvar dlopen_support
Whether @code{dlopen} is supported on the platform.
Set to @samp{yes} or @samp{no}.