public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "PHHargrove at lbl dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/57316] New: [4.8 regresion] build failure in libsanitizer
Date: Fri, 17 May 2013 16:34:00 -0000	[thread overview]
Message-ID: <bug-57316-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57316

            Bug ID: 57316
           Summary: [4.8 regresion] build failure in libsanitizer
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: PHHargrove at lbl dot gov
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

On the same system where I reported bug 55989, I am now experiencing a build
failure in libsanitizer in the released 4.8.0.  As with that earlier bug,
libsanitizer is trying to use something low-level from Linux that did not exist
in older kernel versions.  In this case the "exit_group" systemcall.

I believe a colleague has seen the same problem in 4.8.1 snapshots.

-Paul

libtool: compile:  /home/pcp1/phargrov/data1/GCC/gcc-4.8.0/BLD/./gcc/xgcc
-shared-libgcc -B/home/pcp1/phargrov/data1/GCC/gcc-4.8.0/BLD/./gcc -nostdinc++
-L/home/pcp1/phargrov/data1/GCC/gcc-4.8.0/BLD/i686-pc-linux-gnu/libstdc++-v3/src
-L/home/pcp1/phargrov/data1/GCC/gcc-4.8.0/BLD/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/
-isystem /usr/local/i686-pc-linux-gnu/include -isystem
/usr/local/i686-pc-linux-gnu/sys-include -D_GNU_SOURCE -D_DEBUG
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I.
-I../../../../libsanitizer/sanitizer_common -I ../../../../libsanitizer/include
-Wall -W -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fPIC
-fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables
-fvisibility=hidden -Wno-variadic-macros -I../../libstdc++-v3/include
-I../../libstdc++-v3/include/i686-pc-linux-gnu
-I../../../../libsanitizer/../libstdc++-v3/libsupc++ -g -O2 -D_GNU_SOURCE -MT
sanitizer_linux.lo -MD -MP -MF .deps/sanitizer_linux.Tpo -c
../../../../libsanitizer/sanitizer_common/sanitizer_linux.cc  -fPIC -DPIC -o
.libs/sanitizer_linux.o
../../../../libsanitizer/sanitizer_common/sanitizer_linux.cc: In function 'void
__sanitizer::internal__exit(int)':
../../../../libsanitizer/sanitizer_common/sanitizer_linux.cc:142:11: error:
'__NR_exit_group' was not declared in this scope
   syscall(__NR_exit_group, exitcode);
           ^
make[4]: *** [sanitizer_linux.lo] Error 1


             reply	other threads:[~2013-05-17 16:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 16:34 PHHargrove at lbl dot gov [this message]
2013-05-20  5:45 ` [Bug sanitizer/57316] " jakub at gcc dot gnu.org
2013-05-20 17:55 ` [Bug sanitizer/57316] [4.8 regression] " PHHargrove at lbl dot gov
2013-05-21  9:35 ` [Bug sanitizer/57316] [4.8/4.9 " rguenth at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-08-28 21:29 ` skunk at iskunk dot org
2013-10-16  9:50 ` jakub at gcc dot gnu.org
2013-10-30 12:22 ` rguenth at gcc dot gnu.org
2013-10-30 19:09 ` skunk at iskunk dot org
2013-11-22 10:47 ` rguenth at gcc dot gnu.org
2014-01-22 11:01 ` y.gribov at samsung dot com
2014-01-22 11:06 ` jakub at gcc dot gnu.org
2014-01-22 11:55 ` y.gribov at samsung dot com
2014-01-22 12:05 ` jakub at gcc dot gnu.org
2014-01-22 14:13 ` y.gribov at samsung dot com
2014-01-22 14:22 ` jakub at gcc dot gnu.org
2014-01-22 14:32 ` y.gribov at samsung dot com
2014-01-23 14:34 ` y.gribov at samsung dot com
2014-01-24  7:45 ` [Bug sanitizer/57316] [4.8 " PHHargrove at lbl dot gov
2014-01-24 23:37 ` PHHargrove at lbl dot gov
2014-01-27  7:47 ` y.gribov at samsung dot com
2014-02-05  3:47 ` y.gribov at samsung dot com
2014-05-22  9:00 ` rguenth at gcc dot gnu.org
2014-10-21 16:24 ` y.gribov at samsung dot com
2014-10-21 22:17 ` PHHargrove at lbl dot gov
2014-10-22  5:29 ` skunk at iskunk dot org
2014-10-22  7:59 ` y.gribov at samsung dot com
2014-12-19 13:39 ` jakub at gcc dot gnu.org
2015-06-23  8:42 ` rguenth at gcc dot gnu.org

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-57316-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).