linux-kernel - Re: [PATCH 2/2] trace-cmd: Change the way of getting python ldflags.

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]

Date:   Thu, 8 Feb 2018 18:54:56 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     sztsian@...il.com
Cc:     johannes.berg@...el.com, johannes@...solutions.net,
        linux-kernel@...r.kernel.org, zsun@...hat.com
Subject: Re: [PATCH 2/2] trace-cmd: Change the way of getting python
 ldflags.

On Sun,  4 Feb 2018 11:20:14 +0800
sztsian@...il.com wrote:

> From: Zamir SUN <sztsian@...il.com>
> 
> Prior than this patch, Makefile detects python ldflags using a hardcoded
> python command. It will cause problems if we are building against
> python3 in the future when ldflags for python2 and python3 are
> different. With this patch, python ldflags are detected by
> corresponding python{,3}-config which will detect the right config for
> python plugins.

Thanks, applied.

-- Steve