On Fri, Aug 30, 2013 at 12:44 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On Fri, Aug 30, 2013 at 12:36 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: >> On Fri, Aug 30, 2013 at 12:29:34PM +0200, Sedat Dilek wrote: >>> [ Sorry for being off-topic ] >>> >>> Hey Ingo, >>> >>> can you help, please? >>> >>> I installed so far all missing -dev packages... >>> >>> $ sudo apt-get install libelf-dev libdw-dev libunwind7-dev libslang2-dev >> >> It seems to me the easier way is: >> >> $ apt-get build-dep linux-tools >> > > NO, se B-Ds for Ubuntu-kernel v3.2: > > Build-Depends: dpkg (>= 1.13.19), debhelper (>= 5), gawk > > http://archive.ubuntu.com/ubuntu/pool/main/l/linux-meta/linux-meta_3.2.0.52.62.dsc > >>> ...and then want a perf-only build... >>> >>> [ See tools/Makefile ] >>> >>> $ LANG=C LC_ALL=C make -C tools/ perf_install 2>&1 | tee ../perf_install-log.txt >> >> The way I always build that stuff is simply: >> >> $ cd tools/perf >> $ make -j >> $ cp perf `which perf` >> $ cd - >> > > Please, see advices in 'tools/Makefile': > > @echo 'You can do:' > @echo ' $$ make -C tools/ <tool>_install' > @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.' > > >> No idea about liblk though, never had that issue but maybe something >> like: >> >> $ cd tools/lib/lk/ >> $ make clean >> $ make >> >> will get you a more useful error. dunno, its a fairly trivial little >> library, only a single .c file. > > If looked quickly over diverse Makefile one was saying liblk FORCE, so > it should be built, but is NOT! > > Thanks anyway, Peter for all the hints! > > If you tell me where you discuss perf issues I can describe the problem. > Just as a sidenote for cleaning up (that seems to be the "official" way): $ LANG=C LC_ALL=C make -C tools/ liblk_clean $ LANG=C LC_ALL=C make -C tools/ perf_clean - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
