linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 2/2] libtracefs: Add $(LIBS) to building of shared object library
Date: Thu, 03 Dec 2020 14:06:54 -0500	[thread overview]
Message-ID: <20201203190741.174872816@goodmis.org> (raw)
In-Reply-To: 20201203190652.568672226@goodmis.org

From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>

libtracefs.so relies on libtraceevent.so, but it an application were to
include libtracefs.so, it should not be required to include libtraceevent.so
if that application is not using it. Add the libtraceevent library to the
build of libtracefs.so so that what libtracefs.so uses is included in that
code.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
 scripts/utils.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/utils.mk b/scripts/utils.mk
index d1d5135063fc..1ee283fe4393 100644
--- a/scripts/utils.mk
+++ b/scripts/utils.mk
@@ -61,7 +61,7 @@ do_build_static_lib =				\
 
 do_compile_shared_library =			\
 	($(print_shared_lib_compile)		\
-	$(CC) --shared $^ -Wl,-soname,$(@F) -o $@)
+	$(CC) --shared $^ -Wl,-soname,$(@F) -o $@ $(LIBS))
 
 do_compile_plugin_obj =				\
 	($(print_plugin_obj_compile)		\
-- 
2.28.0



      parent reply	other threads:[~2020-12-03 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 19:06 [PATCH 0/2] libtracefs: Library building fixes Steven Rostedt
2020-12-03 19:06 ` [PATCH 1/2] libtracefs: Remove useless LIBS = -ldl in Makefile Steven Rostedt
2020-12-03 19:06 ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201203190741.174872816@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).