All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10061] New: gcc5.4 buildroot toolchain for powerpc libsanitizer failure
Date: Thu, 13 Jul 2017 03:39:11 +0000	[thread overview]
Message-ID: <bug-10061-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=10061

            Bug ID: 10061
           Summary: gcc5.4 buildroot toolchain for powerpc libsanitizer
                    failure
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: matthew.weber at rockwellcollins.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I'm building the following Buildroot Custom toolchain config and
noticing a libsanitizer failure. 


../../../../libsanitizer/asan/asan_linux.cc: In function ?bool
__asan::AsanInterceptsSignal(int)?:
../../../../libsanitizer/asan/asan_linux.cc:222:20: error: ?SIGSEGV?
was not declared in this scope
   return signum == SIGSEGV && common_flags()->handle_segv;
                    ^
make[6]: *** [asan_linux.lo] Error 1
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-target-libsanitizer] Error 2
make[2]: *** [all] Error 2
make[1]: *** [/accts/mlweber1/target/build/host-gcc-final-5.4.0/.stamp_built]
Error 2
make: *** [_all] Error 2

Config to reproduce:
BR2_powerpc=y
BR2_powerpc_e500mc=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="3.12.37"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_12=y
BR2_GCC_VERSION_5_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_GCC_ENABLE_LTO=y

The resolution looks to be 
https://www.mail-archive.com/gcc-patches at gcc.gnu.org/msg159613.html

I'll get a patch tested and I can confirm so far that the issue goes away in
GCC6 but GCC5.4 has the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-07-13  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  3:39 bugzilla at busybox.net [this message]
2017-07-13  3:40 ` [Buildroot] [Bug 10061] gcc5.4 buildroot toolchain for powerpc libsanitizer failure bugzilla at busybox.net
2017-07-15  9:32 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-10061-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.