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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 24 Dec 2016 15:24:01 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Arnaldo Carvalho de Melo <acme@...hat.com>,
        Jiri Olsa <jolsa@...nel.org>, Wang Nan <wangnan0@...wei.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Michal Marek <mmarek@...e.com>
Subject: Re: [PATCH] tools build: replace $(CC) -E with $(CPP) for pre-processing

Hi Jiri,


2016-12-23 19:59 GMT+09:00 Jiri Olsa <jolsa@...hat.com>:
> On Fri, Dec 23, 2016 at 01:46:42PM +0900, Masahiro Yamada wrote:
>> The top-level Makefile defines:
>>
>>   CPP             = $(CC) -E
>
> hum, so that'd work for running from top level, but I guess
> it fails for compiling from other places..? like tools/perf


I thought users are supposed to build tools from the top-level, but
seems it is not necessarily true
according to your statement.

I am not quite sure how CC, AS, etc. are set-up, then.
Perhaps, relying on Make-builtin variables?

$ make --print-data-base | grep CPP

showed me the default of CPP is

CPP = $(CC) -E

I guess you are more familiar to the tools-build area,
so I follow your decision.


-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists