linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Foley <pefoley2@pefoley.com>,
	LKML <linux-kernel@vger.kernel.org>,
	wangnan0@huawei.com
Subject: Re: [PATCHv3] tools build: Make fixdep parsing wait for last target
Date: Fri, 2 Dec 2016 13:10:56 -0200	[thread overview]
Message-ID: <20161202151056.GA5931@redhat.com> (raw)
In-Reply-To: <20161202091539.GB21304@krava>

Em Fri, Dec 02, 2016 at 10:15:39AM +0100, Jiri Olsa escreveu:
> On Thu, Dec 01, 2016 at 04:53:23PM -0200, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Dec 01, 2016 at 09:48:40AM -0800, Peter Foley escreveu:
> > > On Thu, Dec 1, 2016 at 5:00 AM, Jiri Olsa <jolsa@redhat.com> wrote:
> > > > ok, so v3 actually ;-)

> > > > the v2 was tricky for the case when fixdep is not available,
> > > > so I decided to go with Peter's fix and fixing 'fixdep' tool
> > > > to properly parse out the target in case we hit the ccache
> > > > error.. we need to be able to do it anyway

> > > > please apply this patch before Peter's so we keep clean bisect

> > Doesn't work with ccache installed, but then after reinstalling ccache to check
> > its version, I can't reproduce it anymore, go figure :-\
> > 
> > Can you guys please take a look at tmp.perf/fixdep in my tree and check that
> > the last two patches are the ones that should go upstream and that you are able
> > to build it _with_ ccache installed?
 
> yep, works for me

So I saw it again, while processing Wang's eBPF/llvm patchkit, right after
removing the build dir and starting from scratch, doing that process one more
time made it work, so it looks like a race, and look it is in a HOSTCC bit,
related?

[acme@jouet linux]$ rm -rf /tmp/build/perf/ ; mkdir -p /tmp/build/perf ; make -k O=/tmp/build/perf -C tools/perf install-bin
make: Entering directory '/home/acme/git/linux/tools/perf'
  BUILD:   Doing 'make -j4' parallel build

Auto-detecting system features:
...                         dwarf: [ on  ]
...            dwarf_getlocations: [ on  ]
...                         glibc: [ on  ]
...                          gtk2: [ on  ]
...                      libaudit: [ on  ]
...                        libbfd: [ on  ]
...                        libelf: [ on  ]
...                       libnuma: [ on  ]
...        numa_num_possible_cpus: [ on  ]
...                       libperl: [ on  ]
...                     libpython: [ on  ]
...                      libslang: [ on  ]
...                     libcrypto: [ on  ]
...                     libunwind: [ on  ]
...            libdw-dwarf-unwind: [ on  ]
...                          zlib: [ on  ]
...                          lzma: [ on  ]
...                     get_cpuid: [ on  ]
...                           bpf: [ on  ]

  GEN      /tmp/build/perf/common-cmds.h
  HOSTCC   /tmp/build/perf/fixdep.o
  HOSTLD   /tmp/build/perf/fixdep-in.o
  LINK     /tmp/build/perf/fixdep
  MKDIR    /tmp/build/perf/pmu-events/
  HOSTCC   /tmp/build/perf/pmu-events/json.o
/bin/sh: /tmp/build/perf//fixdep: Permission denied
/home/acme/git/linux/tools/build/Makefile.build:91: recipe for target '/tmp/build/perf/pmu-events/json.o' failed
make[2]: *** [/tmp/build/perf/pmu-events/json.o] Error 1
Makefile.perf:469: recipe for target '/tmp/build/perf/pmu-events/jevents-in.o' failed
make[1]: *** [/tmp/build/perf/pmu-events/jevents-in.o] Error 2
make[1]: *** Waiting for unfinished jobs....
  PERF_VERSION = 4.9.rc6.g165081a
make[1]: *** wait: No child processes.  Stop.
Makefile:108: recipe for target 'install-bin' failed
make: *** [install-bin] Error 2
make: Leaving directory '/home/acme/git/linux/tools/perf'

  reply	other threads:[~2016-12-02 15:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26 22:20 [PATCH] Fix objtool with clang Peter Foley
2016-11-27 16:14 ` Jiri Olsa
2016-11-28  2:43   ` [PATCH v2] " Peter Foley
2016-11-28 11:39     ` Jiri Olsa
2016-11-28 15:00       ` Arnaldo Carvalho de Melo
2016-11-28 15:25         ` Peter Foley
2016-11-28 16:58           ` Jiri Olsa
2016-11-28 19:40             ` Arnaldo Carvalho de Melo
2016-11-28 20:08               ` Jiri Olsa
2016-11-29  9:32               ` Jiri Olsa
2016-11-29  9:58                 ` Jiri Olsa
2016-11-29 14:28               ` Jiri Olsa
2016-11-29 14:33                 ` Arnaldo Carvalho de Melo
2016-11-29 14:39                   ` Jiri Olsa
2016-11-29 14:49                     ` Arnaldo Carvalho de Melo
2016-11-29 15:24                       ` Jiri Olsa
2016-12-01 13:00                       ` [PATCHv3] tools build: Make fixdep parsing wait for last target Jiri Olsa
2016-12-01 17:48                         ` Peter Foley
2016-12-01 18:53                           ` Arnaldo Carvalho de Melo
2016-12-02  8:49                             ` Jiri Olsa
2016-12-02  9:15                             ` Jiri Olsa
2016-12-02 15:10                               ` Arnaldo Carvalho de Melo [this message]
2016-12-06  8:20                         ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-11-28 19:35           ` [PATCH v2] Fix objtool with clang Arnaldo Carvalho de Melo
2016-12-06  8:20     ` [tip:perf/core] tools build: Fix objtool build " tip-bot for Peter Foley

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=20161202151056.GA5931@redhat.com \
    --to=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pefoley2@pefoley.com \
    --cc=wangnan0@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).