linux-kernel - Re: [PATCH 2/9] perf build: Pass O option to Makefile.perf in build-test

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, 14 Jan 2016 11:42:18 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	"Wangnan (F)" <wangnan0@...wei.com>, linux-kernel@...r.kernel.org,
	pi3orama@....com, lizefan@...wei.com, Jiri Olsa <jolsa@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>
Subject: Re: [PATCH 2/9] perf build: Pass O option to Makefile.perf in
 build-test

Em Thu, Jan 14, 2016 at 03:37:28PM +0100, Jiri Olsa escreveu:
> On Thu, Jan 14, 2016 at 11:28:23AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Jan 14, 2016 at 05:56:06PM +0800, Wangnan (F) escreveu:
> > > >>+	cmd="cd $(PERF) && make -f $(MK) $(PARALLEL_OPT) $(O_OPT) DESTDIR=$$TMP_DEST $($@)"; \
> > > >hum, but this set is to test make without O=... so why would you set it?
> > > >run_O is the target for O=... tests
> > > 
> > > I have strong motivation to avoid polluting source directory.
> > 
> > yeah!
> 
> heh, I knew you'd be excited ;-) but does that actually mean
> that build-test will never run tests in source directory?

Humm, I think this is something to be supported, but source code
repository polution is really bad and a pet peeve I have with
build-test, so the fact that Wang is working to remove that limitation
is indeed exciting :-)

- Arnaldo