[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150916173025.7913543a@canb.auug.org.au>
Date: Wed, 16 Sep 2015 17:30:25 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Jiri Olsa <jolsa@...hat.com>
Cc: 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,
Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: linux-next: build failure after merge of the tip tree
Hi Jiri,
On Wed, 16 Sep 2015 08:38:17 +0200 Jiri Olsa <jolsa@...hat.com> wrote:
>
> > > Also, building perf seems to ignore O=<dir> on the make invocation.
> > > Is that expected?
> >
> > hum, not sure about this one.. I'm not using it, but we have
> > tests for this and I thought we're ok.. I'll check
>
> seems to work on latest Arnaldo's perf/core,
> what command line failed for you?
>
> [jolsa@...va perf]$ make O=/tmp/krava/
> ...
> [jolsa@...va perf]$ ll /tmp/krava/perf
> -rwxrwxr-x. 1 jolsa jolsa 12669704 Sep 16 08:36 /tmp/krava/perf
Thanks for the hint. I was using a relative path and starting in the
top of the kernel tree, so:
$ cd kernel
$ mkdir ../perf
$ make -s -C tools/perf JOBS=24 O=../perf
put everything in toos/perf (no suprise really)
I will change my script to use an absolute path (which I checked does
work fine). Sorry for the noise.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
--
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