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] [day] [month] [year] [list]
Message-ID: <CA+icZUXBMOH9s+ybTXWo1R1YOp+AbsouGLoz_OwcCV6-MbkdUw@mail.gmail.com>
Date:	Fri, 30 Aug 2013 17:24:46 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [3.11-rc7] Building perf-only the "official" way seems to be BROKEN?

On Fri, Aug 30, 2013 at 4:54 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Fri, Aug 30, 2013 at 4:28 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> [...]
>>
>>> [ BUILD PERF-ONLY ]
>>>
>>> So, I have finished a Linux-kernel build and wanted to build perf
>>> (from tools-dir) ONLY!
>>>
>>> I followed the advices (I am a "good" guy) seen for example in the
>>> "tools/Makefile" file.
>>>
>>> [ tools/Makefile ]
>>> ...
>>>         @echo 'You can do:'
>>>         @echo ' $$ make -C tools/ <tool>_install' <--- NOTE THIS ONE!
>>>         @echo ''
>>>         @echo '  from the kernel command line to build and install one of'
>>>         @echo '  the tools above'
>>>         @echo ''
>>>         @echo '  $$ make tools/install'
>>>         @echo ''
>>>         @echo '  installs all tools.'
>>> ...
>>>
>>> OK, so I did this for a perf-only build...
>>>
>>>
>>>    $ LANG=C LC_ALL=C make -C tools/ perf_install 2>&1 | tee ../build-perf.txt
>>>
>>> ...this breaks like this...
>>>
>>> ...
>>> make[2]: Entering directory
>>> `/home/wearefam/src/linux-kernel/linux/tools/lib/traceevent'
>>> make[2]: Leaving directory
>>> `/home/wearefam/src/linux-kernel/linux/tools/lib/traceevent'
>>>     LINK perf
>>> gcc: error: /home/wearefam/src/linux-kernel/linux/tools/lib/lk/liblk.a:
>>> No such file or directory
>>> make[1]: *** [perf] Error 1
>>> make[1]: Leaving directory `/home/wearefam/src/linux-kernel/linux/tools/perf'
>>> make: *** [perf_install] Error 2
>>>
>>
>> [ From #linux-rt (OFTC) ]
>>
>> [16:17] <acme> dileks_webchat, there are many, many ways to build the tools
>> [16:17] <acme> the one I use is:
>> [16:17] <acme> make O=/tmp/build/perf -C tools/perf install
>> [16:19] <dileks_webchat> acme:  make -C tools/perf install works as
>> expected. interesting :-)
>>
>
> Attached patch seems to fix the issue when building perf this way...
>
>    $ make -C tools/ perf_install
>

I have sent a patch ("[PATCH] tools: perf: Fix liblk not built when
using perf_install target") in [1].

- Sedat -

[1] http://marc.info/?l=linux-kernel&m=137787594331047&w=2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ