public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55313] libsanitizer cannot be installed
Date: Mon, 19 Nov 2012 21:16:00 -0000 [thread overview]
Message-ID: <bug-55313-4-S9DV4o1kPL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55313-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55313
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-19 21:15:30 UTC ---
> Please show me the outputs of
>
> # tail x86_64-pc-linux-gnu/libsanitizer/asan/libasan.la
# Should we warn about portability when linking against -modules?
shouldnotlink=no
# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''
# Directory that this library needs to be installed in:
libdir='/usr/gnat/lib/../lib64'
relink_command="(cd
/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libsanitizer/asan;
/bin/bash
/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libsanitizer/libtool
--tag CXX --mode=relink
/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/./gcc/g++
-B/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/./gcc/ -nostdinc++
-nostdinc++
-I/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/src/libstdc++-v3/libsupc++
-I/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/src/libstdc++-v3/include/backward
-I/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/src/libstdc++-v3/testsuite/util
-L/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/red.a/gnatmail/gcc-x/build-red/x86_64-linux/gnat/obj/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/usr/gnat/x86_64-pc-linux-gnu/bin/ -B/usr/gnat/x86_64-pc-linux-gnu/lib/
-isystem /usr/gnat/x86_64-pc-linux-gnu/include -isystem
/usr/gnat/x86_64-pc-linux-gnu/sys-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
-Wno-c99-extensions -O2 -g -D_GNU_SOURCE -version-info 0:0:0 -lpthread -ldl -o
libasan.la -rpath /usr/gnat/lib/../lib64 asan_allocator.lo asan_interceptors.lo
asan_mac.lo asan_malloc_mac.lo asan_new_delete.lo asan_posix.lo asan_rtl.lo
asan_stats.lo asan_thread_registry.lo asan_globals.lo asan_linux.lo
asan_malloc_linux.lo asan_malloc_win.lo asan_poisoning.lo asan_report.lo
asan_stack.lo asan_thread.lo asan_win.lo
../sanitizer_common/libsanitizer_common.la ../interception/libinterception.la
../../libstdc++-v3/src/libstdc++.la @inst_prefix_dir@)"
> # tail x86_64-pc-linux-gnu/libstdc++-v3/src/libstdc++.la
# Should we warn about portability when linking against -modules?
shouldnotlink=no
# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''
# Directory that this library needs to be installed in:
libdir='/usr/gnat/lib/../lib64'
> Are you using Debian? What is the minimum configure option to trigger this?
Nope, this occurs on a x86/Linux box with RHEL 5.8 and on a x86-64/Linux box
with SLES 10. Both automated builds. It's maybe the relative path to the
configure script, but this works for all the other libraries.
next prev parent reply other threads:[~2012-11-19 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:39 [Bug other/55313] New: " ebotcazou at gcc dot gnu.org
2012-11-13 14:45 ` [Bug other/55313] " hjl.tools at gmail dot com
2012-11-16 14:08 ` ebotcazou at gcc dot gnu.org
2012-11-16 15:36 ` hjl.tools at gmail dot com
2012-11-16 15:38 ` hjl.tools at gmail dot com
2012-11-19 9:58 ` ebotcazou at gcc dot gnu.org
2012-11-19 20:55 ` hjl.tools at gmail dot com
2012-11-19 21:16 ` ebotcazou at gcc dot gnu.org [this message]
2012-11-20 0:15 ` hjl.tools at gmail dot com
2012-11-22 9:09 ` ebotcazou at gcc dot gnu.org
2012-11-22 14:15 ` [Bug sanitizer/55313] " hjl.tools at gmail dot com
2012-11-23 23:11 ` hjl.tools at gmail 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-55313-4-S9DV4o1kPL@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).