You should fix perf-script.py replace sys.path.append(os.environ['PERF_EXEC_PATH'] + '/scripts/python/Perf-Trace-Util/lib/Perf/Trace') with
sys.path.append(os.getcwd()+"/tools/perf/scripts/python/ Perf-Trace-Util/lib/Perf/Trace") this string instruct python interpreter where to find modules to load. Please check that "perf script" command works correctly (output all sample records from perf.data file) Mikhail. 2013/8/30 Peipei Wang <wangpeipei...@gmail.com>: > Hi Mikhail, > > Yes, you are right. I could use perf now. But I get errors again running > "perf script -s perf-script.py". Here it is: > perf script -s perf-script.py > Traceback (most recent call last): > File "perf-script.py", line 18, in <module> > from Core import * > ImportError: No module named Core > > I do have the module Core.py in the directory of > tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace > > Is there anything else I should pay attention to when using this? > > Best wishes. > Yours, > Wang Peipei > > > On Fri, Aug 30, 2013 at 9:33 AM, David Ahern <dsah...@gmail.com> wrote: >> >> On 8/29/13 10:28 PM, Mikhail Kulemin wrote: >>> >>> You can ignote message about Android. As far as I understand form >>> output you should see compiled executable of perf in tools/perf >>> directory. Please check it. >> >> >> Yes, you can ignore that message during the CHK - it's just probing for >> build options. >> >> David > > -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html