linux-kernel - Re: [PATCHv2 01/10] tools lib traceevent: Use LDFLAGS in the build commands

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181122093006.GD15953@krava>
Date:   Thu, 22 Nov 2018 10:30:06 +0100
From:   Jiri Olsa <jolsa@...hat.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Jiri Olsa <jolsa@...nel.org>, lkml <linux-kernel@...r.kernel.org>,
        Tzvetomir Stoyanov <tz.stoyanov@...il.com>,
        "Herton R. Krzesinski" <herton@...hat.com>
Subject: Re: [PATCHv2 01/10] tools lib traceevent: Use LDFLAGS in the build
 commands

On Fri, Nov 16, 2018 at 02:01:58PM +0100, Jiri Olsa wrote:
> On Wed, Oct 17, 2018 at 10:23:41AM -0400, Steven Rostedt wrote:
> > On Tue, 16 Oct 2018 17:45:26 +0200
> > Jiri Olsa <jolsa@...hat.com> wrote:
> > 
> > > On Tue, Oct 16, 2018 at 11:21:36AM -0400, Steven Rostedt wrote:
> > > > 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?  
> > > 
> > > yep, sry.. v2 attached
> > > 
> > 
> > Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
> 
> Arnaldo,
> could you pull in this one?

ping, thanks

jirka