All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [GIT PULL] tools/perf/build: Speed up the perf build system
Date: Thu, 10 Oct 2013 16:50:14 -0300	[thread overview]
Message-ID: <20131010195014.GJ28369@ghostprotocols.net> (raw)
In-Reply-To: <20131010192608.GI28369@ghostprotocols.net>

Em Thu, Oct 10, 2013 at 04:26:08PM -0300, Arnaldo Carvalho de Melo escreveu:
> Two problems:
> 
> the message:
> 
>   BUILD:   Doing 'make -j1' parallel build
> 
> Looks funny: 'parallel' && -j1? :-)
> 
> This is on fedora12, on a kvm guest, nfs mounting /home/acme/git, all works
> well up to the liblk.a part, cloning it to do it without NFS to continue
> testing the integration of acme/perf/core with the build speedup patches.

<SNIP>

>   AR       liblk.a
> rm: cannot remove `liblk.a': Permission denied
> make[2]: *** [liblk.a] Error 1
> make[1]: *** [/tmp/build/perf/liblk.a] Error 2
> make: *** [install] Error 2
> make: Leaving directory `/home/acme/git/linux/tools/perf'
> [acme@fedora12 linux]$ fg
> -bash: fg: current: no such job
> [acme@fedora12 linux]$ vim tools/perf/Makefile.perf 

/me scratches head, tried this on another kvm guest, ubuntu 13.04,
x86_64, works as expected, but stumbled in another problem:

acme@ubuntu-acme:~/git/linux$ time make -C tools/perf -f tests/make
make: Entering directory `/home/acme/git/linux/tools/perf'
make[3]: *** No rule to make target
`/home/git/linux/tools/lib/traceevent/trace-seq.c', needed by
`.trace-seq.d'.  Stop.
make[2]: ***
[/home/acme/git/linux/tools/lib/traceevent/libtraceevent.a-clean] Error
2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [clean] Error 2
make: *** [make_pure] Error 2
make: Leaving directory `/home/acme/git/linux/tools/perf'

real	0m0.254s
user	0m0.064s
sys	0m0.084s
acme@ubuntu-acme:~/git/linux$

And this does work on a RHEL6 box, continue to investigate...

- Arnaldo

  reply	other threads:[~2013-10-10 19:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  7:01 [GIT PULL] tools/perf/build: Speed up the perf build system Ingo Molnar
2013-10-09 14:38 ` Arnaldo Carvalho de Melo
2013-10-09 14:51   ` Ingo Molnar
2013-10-09 15:00     ` [PATCH] tools/perf/build: Fix non-existent build directory handling Ingo Molnar
2013-10-15  5:33       ` [tip:perf/core] " tip-bot for Ingo Molnar
2013-10-09 19:16     ` [GIT PULL] tools/perf/build: Speed up the perf build system Arnaldo Carvalho de Melo
2013-10-09 19:38       ` Arnaldo Carvalho de Melo
2013-10-10  5:42       ` [PATCH] tools/perf/build: Fix redirection printouts Ingo Molnar
2013-10-15  5:31         ` [tip:perf/core] perf tools: " tip-bot for Ingo Molnar
2013-10-10  6:10       ` [PATCH] tools/perf/build: Pass through DEBUG parameter Ingo Molnar
2013-10-10 19:26     ` [GIT PULL] tools/perf/build: Speed up the perf build system Arnaldo Carvalho de Melo
2013-10-10 19:50       ` Arnaldo Carvalho de Melo [this message]
2013-10-10 20:06         ` Arnaldo Carvalho de Melo
2013-10-10 22:13           ` Jiri Olsa
2013-10-10 22:29             ` David Ahern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131010195014.GJ28369@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.