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: <20160115151244.GA18367@kernel.org>
Date:	Fri, 15 Jan 2016 12:12:44 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	pi3orama <pi3orama@....com>
Cc:	Jiri Olsa <jolsa@...hat.com>, Wang Nan <wangnan0@...wei.com>,
	linux-kernel@...r.kernel.org, lizefan@...wei.com
Subject: Re: [PATCH v3 0/9] perf build: Make build-test faster

Em Fri, Jan 15, 2016 at 10:54:47PM +0800, pi3orama escreveu:
> 发自我的 iPhone
> > 在 2016年1月15日,下午10:36,Arnaldo Carvalho de Melo <acme@...nel.org> 写道:
> > tests/make:7: recipe for target 'all' failed
> > make[1]: *** [all] Error 2
> > Makefile:81: recipe for target 'build-test' failed
> > make: *** [build-test] Error 2
> > make: Leaving directory '/home/git/linux/tools/perf'
> > [acme@zoo linux]$ find . -name "*.so"
> > ./tools/perf/python_ext_build/lib/perf.so
> > ./tools/perf/python/perf.so
> > [acme@zoo linux]$
> > 
> > I.e. the test -f follows O=, but the process to generate python/perf.so
> > doesn't and ends up pollutting the source tree.
 
> Is your source directory already polluted
> before this test?

Yeah, that seems to have been the case, I tried reproducing this problem
using just the python perf.so target, after cleaning the sources and it
worked, then I cleaned it again and I am re-running build-test O= and it
is working so far.

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ