[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161207185632.GA24040@gmail.com>
Date: Wed, 7 Dec 2016 19:56:32 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...hat.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Peter Foley <pefoley2@...oley.com>,
Wang Nan <wangnan0@...wei.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the tip tree
* Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> Em Wed, Dec 07, 2016 at 09:12:15AM +0100, Jiri Olsa escreveu:
> > On Wed, Dec 07, 2016 at 08:45:14AM +0100, Ingo Molnar wrote:
> >
> > SNIP
> >
> > > * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > > Hi all,
> > > >
> > > > After merging the tip tree, today's linux-next build (powerpc64le perf)
> > > > failed like this:
> > > >
> > > > LINK /home/sfr/next/perf/fixdep
> > > > /bin/sh: 1: /home/sfr/next/perf//fixdep: Permission denied
> > > > tools/build/Makefile.build:91: recipe for target '/home/sfr/next/perf/pmu-events/jevents.o' failed
> > > >
> > > > $ ls -l /home/sfr/next/perf/fixdep
> > > > -rwxr-xr-x 1 sfr users 71104 Dec 7 12:26 /home/sfr/next/perf/fixdep
> > > >
> > > > I am not sure what caused this, but redoing the build succeeded, so I
> > > > have just filed this report and left it for today.
> >
> > this seems to be the rare race issue caused by missing fixdep dependency,
> > caused probably by recompiling of fixdep because of its change in the merge
> >
> > Arnaldo already carries a fix for this in his latest perf/core, where
> > we moved the fixdep compilation on top of everything to kill any future
> > race due to missing fixdep dependency
>
> I'll push it today, will stop processing other stuff now and prepare a
> pull request,
Thanks - I pushed the fixes towards linux-next, so tomorrow's (today's) linux-next
build should not trigger this build race.
Thanks,
Ingo
Powered by blists - more mailing lists