While Libtool tries to hide as many platform-specific features as possible, some have to be taken into account when configuring either the Libtool package or a libtoolized package.
LDFLAGS=-Wl,-brtl
for the latter style.
AR=/usr/bin/ar LD=/usr/bin/ld NM='/usr/bin/nm -B'
.
/bin/sh
is very slow due to its inefficient handling
of here-documents. A modern shell is preferable:
CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL $CONFIG_SHELL ./configure [...]
CXX='pgCC --one_instantiation_per_object'
and avoid parallel make
.
-fsanitize=address
you need to specify the -lasan
library,
like so: g++ -o libx.la -fsanitize=address -lasan -rpath [...]
.
MACOSX_DEPLOYMENT_TARGET
is set to
10.3 or later at configure
time. See rdar://problem/4135857
for more information on this issue.
sed
programs are horribly broken, and cannot handle
libtool’s requirements, so users may report unusual problems. There
is no workaround except to install a working sed
(such as GNU sed)
on these systems.
cc
programs emits copyright
on standard error that confuse tests on size of conftest.err. The
workaround is to specify CC
when run configure with
CC='cc -Hnocopyr'
.
gcc
provided by Marco Walther.
libtool
sometimes guesses the wrong paths that the linker and dynamic linker search by
default. If this occurs for the dynamic library path, you may use the
LT_SYS_LIBRARY_PATH
environment variable to adjust. Otherwise, at
configure
time you may override libtool’s guesses by setting the
autoconf
cache variables lt_cv_sys_lib_search_path_spec
and
lt_cv_sys_lib_dlsearch_path_spec
respectively.