[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181016112136.3a72a452@gandalf.local.home>
Date: Tue, 16 Oct 2018 11:21:36 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Olsa <jolsa@...nel.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Tzvetomir Stoyanov <tz.stoyanov@...il.com>,
"Herton R. Krzesinski" <herton@...hat.com>
Subject: Re: [PATCH 01/10] tools lib traceevent: Use LDFLAGS in the build
commands
On Tue, 16 Oct 2018 17:06:06 +0200
Jiri Olsa <jolsa@...nel.org> wrote:
> So user could specify outside LDFLAGS values.
>
> Cc: Tzvetomir Stoyanov (VMware) <tz.stoyanov@...il.com>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>
> ---
> tools/lib/traceevent/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/lib/traceevent/Makefile b/tools/lib/traceevent/Makefile
> index 0b4e833088a4..e535073c94ce 100644
> --- a/tools/lib/traceevent/Makefile
> +++ b/tools/lib/traceevent/Makefile
> @@ -174,7 +174,7 @@ $(TE_IN): force
> $(Q)$(MAKE) $(build)=libtraceevent
>
> $(OUTPUT)libtraceevent.so.$(EVENT_PARSE_VERSION): $(TE_IN)
> - $(QUIET_LINK)$(CC) --shared $^ -Wl,-soname,libtraceevent.so.$(EP_VERSION) -o $@
> + $(QUIET_LINK)$(CC) --shared $(LDFLAGS) $^ -Wl,-soname,libtraceevent.so.$(EP_VERSION) -o $@
> @ln -sf $(@F) $(OUTPUT)libtraceevent.so
> @ln -sf $(@F) $(OUTPUT)libtraceevent.so.$(EP_VERSION)
>
> @@ -193,7 +193,7 @@ $(PLUGINS_IN): force
> $(Q)$(MAKE) $(build)=$(plugin_obj)
>
> $(OUTPUT)%.so: $(OUTPUT)%-in.o
> - $(QUIET_LINK)$(CC) $(CFLAGS) -shared -nostartfiles -o $@ $^
> + $(QUIET_LINK)$(CC) -shared $(LDFLAGS) -nostartfiles -o $@ $^
I'm guessing that the CFLAGS are not needed here, but shouldn't that
also be mentioned in the change log?
-- Steve
>
> define make_version.h
> (echo '/* This file is automatically generated. Do not modify. */'; \
Powered by blists - more mailing lists