[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140113180022.GC5318@ghostprotocols.net>
Date: Mon, 13 Jan 2014 15:00:22 -0300
From: Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH] perf tools: Fix build error on zfree()
Em Thu, Jan 09, 2014 at 11:07:59PM +0900, Namhyung Kim escreveu:
> It failed to build perf on my ubuntu 10.04 box (gcc 4.4.3):
>
> CC util/strlist.o
> cc1: warnings being treated as errors
> util/strlist.c: In function ‘str_node__delete’:
> util/strlist.c:42: error: dereferencing type-punned pointer will break strict-aliasing rules
> util/strlist.c:42: error: dereferencing type-punned pointer will break strict-aliasing rules
> CC util/strfilter.o
> make: *** [util/strlist.o] Error 1
>
> CC util/srcline.o
> cc1: warnings being treated as errors
> util/srcline.c: In function ‘addr2line_init’:
> util/srcline.c:132: error: dereferencing type-punned pointer will break strict-aliasing rules
> util/srcline.c:132: error: dereferencing type-punned pointer will break strict-aliasing rules
> util/srcline.c: In function ‘addr2line_cleanup’:
> util/srcline.c:143: error: dereferencing type-punned pointer will break strict-aliasing rules
> util/srcline.c:143: error: dereferencing type-punned pointer will break strict-aliasing rules
> make: *** [util/srcline.o] Error 1
>
> It seems it only allows to remove 'const' qualifier.
Humm, I just tried building it here on:
acme@...ntu13:~/git/linux$ uname -a
Linux ubuntu13 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
acme@...ntu13:~/git/linux$ cat /etc/debian_version
wheezy/sid
acme@...ntu13:~/git/linux$
acme@...ntu13:~/git/linux$ make O=/tmp/build/perf -C tools/perf install
make: Entering directory `/home/acme/git/linux/tools/perf'
BUILD: Doing 'make -j4' parallel build
Auto-detecting system features:
... backtrace: [ on ]
... dwarf: [ OFF ]
... fortify-source: [ on ]
... glibc: [ on ]
... gtk2: [ OFF ]
... gtk2-infobar: [ OFF ]
... libaudit: [ OFF ]
... libbfd: [ OFF ]
... libelf: [ OFF ]
... libelf-getphdrnum: [ OFF ]
... libelf-mmap: [ OFF ]
... libnuma: [ OFF ]
... libperl: [ OFF ]
... libpython: [ OFF ]
... libpython-version: [ OFF ]
... libslang: [ OFF ]
... libunwind: [ OFF ]
... on-exit: [ on ]
... stackprotector-all: [ on ]
... timerfd: [ on ]
config/Makefile:276: No libelf found, disables 'probe' tool, please install elfutils-libelf-devel/libelf-dev
config/Makefile:327: No libunwind found, disabling post unwind support. Please install libunwind-dev[el] >= 1.1
config/Makefile:350: No libaudit.h found, disables 'trace' tool, please install audit-libs-devel or libaudit-dev
config/Makefile:364: slang not found, disables TUI support. Please install slang-devel or libslang-dev
config/Makefile:377: GTK2 not found, disables GTK2 support. Please install gtk2-devel or libgtk2.0-dev
config/Makefile:438: The path '/usr/bin/python-config' is not executable.
config/Makefile:442: No python-config tool was found
config/Makefile:442: Python support will not be built
config/Makefile:532: No numa.h found, disables 'perf bench numa mem' benchmark, please install numactl-devel/libnuma-devel/libnuma-dev
MKDIR /tmp/build/perf/arch
<SNIP>
CC /tmp/build/perf/util/strlist.o
<SNIP>
CC /tmp/build/perf/util/parse-events.o
CC /tmp/build/perf/util/parse-events-flex.o
AR /tmp/build/perf/libperf.a
LINK /tmp/build/perf/perf
INSTALL binaries
INSTALL libexec
INSTALL perf-archive
INSTALL perf_completion-script
INSTALL tests
make: Leaving directory `/home/acme/git/linux/tools/perf'
acme@...ntu13:~/git/linux$
Works just fine, can you provide more details about your system? Is it 32-bit?
I'm installing more devel packages to this just installed 64-bit VM system and
will install another VM with a 32-bit Ubuntu with the same version as you.
- Arnaldo
--
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