> +If you, by mistake, use @code{LIB<@var{NAME}>} instead of > +@code{LTLIB<@var{NAME}>} when linking with libtool, you will observe that the > +binaries created in the build dir will prefer the shared libraries in the > +installation directories over the shared libraries in the build dir; this can > +lead to all sorts of build failures, test failures, or crashes! > > It would be more correct to refer to the "wrapper scripts created in the > build dir". Well, the 'readelf' command from [1] showed that the BUILD_DIR/.libs/lt-PROGRAM executable had a wrong rpath. Whether libtool creates this binary directly or through the intermediary of a wrapper script and a relink_command, is irrelevant for the purpose of this piece of documentation.
Right. Never mind then :)