public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59106] Failure to link against static libasan
Date: Mon, 18 Nov 2013 06:49:00 -0000	[thread overview]
Message-ID: <bug-59106-4-3DN4O8l3pg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59106-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Yury Gribov <y.gribov at samsung dot com> ---
Sent to gcc-patches: http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01990.html

As for libubsan, it does not seem to support static link anyway:

 /home/ygribov/install/gcc-master/bin/gcc -g repro.i -fsanitize=undefined
-static-libubsan
 ...
 /sanitizer_linux_libcdep.cc:71: undefined reference to `pthread_getattr_np'
 /sanitizer_linux_libcdep.cc:74: undefined reference to `pthread_attr_getstack'
 /sanitizer_linux_libcdep.cc:85: undefined reference to `dlsym'
 ...

Once it does, we can go with the same per-file flags hack that we do e.g. in
libstdc++-v3/src/Makefile.am.


  parent reply	other threads:[~2013-11-18  6:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  9:26 [Bug sanitizer/59106] New: " y.gribov at samsung dot com
2013-11-13  9:34 ` [Bug sanitizer/59106] " y.gribov at samsung dot com
2013-11-13  9:39 ` kcc at gcc dot gnu.org
2013-11-13 11:18 ` y.gribov at samsung dot com
2013-11-13 11:24 ` kcc at gcc dot gnu.org
2013-11-13 11:53 ` y.gribov at samsung dot com
2013-11-13 11:57 ` kcc at gcc dot gnu.org
2013-11-13 12:02 ` jakub at gcc dot gnu.org
2013-11-13 12:38 ` kcc at gcc dot gnu.org
2013-11-13 12:39 ` y.gribov at samsung dot com
2013-11-15 12:47 ` kcc at gcc dot gnu.org
2013-11-15 12:53 ` y.gribov at samsung dot com
2013-11-15 13:30 ` kcc at gcc dot gnu.org
2013-11-18  6:49 ` y.gribov at samsung dot com [this message]
2013-11-18  7:19 ` kcc at gcc dot gnu.org
2013-11-18  7:39 ` jakub at gcc dot gnu.org
2013-11-18  8:03 ` ygribov at gcc dot gnu.org
2013-11-18  8:55 ` y.gribov at samsung dot com
2013-11-28 12:20 ` ygribov at gcc dot gnu.org
2013-11-28 12:22 ` y.gribov at samsung dot com

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-59106-4-3DN4O8l3pg@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).