On Mon, Dec 2, 2013 at 5:12 PM, Konstantin Serebryany <konstantin.s.serebry...@gmail.com> wrote:
>>>> Does it support using libbacktrace in GCC? >>> >>> Not on it's own, but the support in the upstream maintained files >>> is there, so hopefully it will be just a matter of follow-up patch >>> with configury/Makefile etc. stuff, I'll work on it once the merge is >>> committed. >>> >>> What is more important now is to test the patch Kostya posted on non-x86_64 >>> targets and/or older kernel headers (say RHEL5, older SLES, etc.). >> >> Unfortunately, the build breaks on CentOS 5.10 (= RHEL5) with: >> >> libtool: compile: /home/uros/gcc-build-xxx/./gcc/xgcc -shared-libgcc >> -B/home/uros/gcc-build-xxx/./gcc -nostdinc++ >> -L/home/uros/gcc-build-xxx/x86_64-unknown-linux-gnu/libstdc++-v3/src >> -L/home/uros/gcc-build-xxx/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs >> -L/home/uros/gcc-build-xxx/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs >> -B/usr/local/x86_64-unknown-linux-gnu/bin/ >> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem >> /usr/local/x86_64-unknown-linux-gnu/include -isystem >> /usr/local/x86_64-unknown-linux-gnu/sys-include -D_GNU_SOURCE -D_DEBUG >> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS >> -I. -I../../../../gcc-svn/trunk/libsanitizer/sanitizer_common -I >> ../../../../gcc-svn/trunk/libsanitizer/include -Wall -W >> -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fPIC >> -fno-builtin -fno-exceptions -fno-rtti -fomit-frame-pointer >> -funwind-tables -fvisibility=hidden -Wno-variadic-macros >> -I../../libstdc++-v3/include >> -I../../libstdc++-v3/include/x86_64-unknown-linux-gnu >> -I../../../../gcc-svn/trunk/libsanitizer/../libstdc++-v3/libsupc++ -g >> -O2 -D_GNU_SOURCE -MT sanitizer_platform_limits_linux.lo -MD -MP -MF >> .deps/sanitizer_platform_limits_linux.Tpo -c >> ../../../../gcc-svn/trunk/libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc >> -fPIC -DPIC -o .libs/sanitizer_platform_limits_linux.o >> ../../../../gcc-svn/trunk/libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc:54:30: >> fatal error: linux/perf_event.h: No such file or directory >> #include <linux/perf_event.h> > > Sounds familiar. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59068 > Do things work for you w/o my patch in fresh trunk? No, so your patch doesn't regress anything. I can configure with --disable-libsanitizer to skip build of libsanitizer, although it would be nice to support RHEL5 derived long-term distributions. > Is there a way to test gcc in such environment w/o setting up VMs > (e.g. chroot, or some such)? Maybe gcc compile farm has linux-2.6.18 machine available? Uros.
