aboutsummaryrefslogtreecommitdiffstats
path: root/lib/libuutil/Makefile.am
diff options
context:
space:
mode:
authorArvind Sankar <[email protected]>2020-07-06 16:01:29 -0400
committerBrian Behlendorf <[email protected]>2020-07-10 14:26:32 -0700
commit3e597dee1128db8907a2b757c675c41cfdbf21aa (patch)
tree4854f380b44a21feb9fb9e2dc0664da2d9868db1 /lib/libuutil/Makefile.am
parentaf6591622696bcb4e46702da07923e909db99f30 (diff)
Use abs_top_builddir when referencing libraries
libtool stores absolute paths in the dependency_libs component of the .la files. If the Makefile for a dependent library refers to the libraries by relative path, some libraries end up duplicated on the link command line. As an example, libzfs specifies libzfs_core, libnvpair and libuutil as dependencies to be linked in. The .la file for libzfs_core also specifies libnvpair, but using an absolute path, with the result that libnvpair is present twice in the linker command line for producing libzfs. While the only thing this causes is to slightly slow down the linking, we can avoid it by using absolute paths everywhere, including for convenience libraries just for consistency. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Arvind Sankar <[email protected]> Closes #10538
Diffstat (limited to 'lib/libuutil/Makefile.am')
-rw-r--r--lib/libuutil/Makefile.am4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/libuutil/Makefile.am b/lib/libuutil/Makefile.am
index 099446ca2..4143a190b 100644
--- a/lib/libuutil/Makefile.am
+++ b/lib/libuutil/Makefile.am
@@ -16,8 +16,8 @@ USER_C = \
libuutil_la_SOURCES = $(USER_C)
libuutil_la_LIBADD = \
- $(top_builddir)/lib/libavl/libavl.la \
- $(top_builddir)/lib/libspl/libspl.la
+ $(abs_top_builddir)/lib/libavl/libavl.la \
+ $(abs_top_builddir)/lib/libspl/libspl.la
libuutil_la_LIBADD += $(LTLIBINTL)