public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/28811] --with-pic vs static libraries and libstdc++
Date: Mon, 05 Nov 2012 23:42:00 -0000	[thread overview]
Message-ID: <bug-28811-4-HVz7jRY7YR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28811-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #21 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-11-05 23:42:36 UTC ---
Author: bkoz
Date: Mon Nov  5 23:42:32 2012
New Revision: 193195

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193195
Log:
2012-11-05  Benjamin Kosnik  <bkoz@redhat.com>

        PR libstdc++/28811
        PR libstdc++/54482
        * configure.ac (glibcxx_lt_pic_flag,
          glibcxx_compiler_pic_flag,
          glibcxx_compiler_shared_flag): New. Use them.
        (lt_prog_compiler_pic_CXX): Set via glibcxx_*_flag(s) above.
        (pic_mode): Set to default.
        (PIC_CXXFLAGS): Remove.
        * Makefile.am (PICFLAG, PICFLAG_FOR_TARGET): Remove. Comment.
        * libsupc++/Makefile.am: Use glibcxx_ld_pic_flag and
          glibcxx_compiler_shared_flag. Comment.
        * src/c++11/Makefile.am: Same.
        * src/c++98/Makefile.am: Same.
        * src/Makefile.am: Use glibcxx_compiler_pic_flag.

        * Makefile.in: Regenerated.
        * aclocal.m4: Same.
        * configure: Same.
        * doc/Makefile.in: Same.
        * include/Makefile.in: Same.
        * libsupc++/Makefile.in: Same.
        * po/Makefile.in: Same.
        * python/Makefile.in: Same.
        * src/Makefile.in: Same.
        * src/c++11/Makefile.in: Same.
        * src/c++98/Makefile.in: Same.
        * testsuite/Makefile.in: Same.

        * src/c++11/compatibility-atomic-c++0x.cc: Use
          _GLIBCXX_SHARED instead of PIC to designate shared-only
          code blocks.
        * src/c++11/compatibility-c++0x.cc: Same.
        * src/c++11/compatibility-thread-c++0x.cc: Same.
        * src/c++98/compatibility-list-2.cc: Same.
        * src/c++98/compatibility.cc: : Same.

        * testsuite/17_intro/shared_with_static_deps.cc: New.

        * doc/xml/manual/build_hacking.xml: Separate configure from
        make/build issues, add build details.


Added:
   
branches/gcc-4_7-branch/libstdc++-v3/testsuite/17_intro/shared_with_static_deps.cc
Modified:
    branches/gcc-4_7-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_7-branch/libstdc++-v3/Makefile.am
    branches/gcc-4_7-branch/libstdc++-v3/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/configure
    branches/gcc-4_7-branch/libstdc++-v3/configure.ac
    branches/gcc-4_7-branch/libstdc++-v3/doc/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/doc/xml/manual/build_hacking.xml
    branches/gcc-4_7-branch/libstdc++-v3/include/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/libsupc++/Makefile.am
    branches/gcc-4_7-branch/libstdc++-v3/libsupc++/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/po/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/python/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/src/Makefile.am
    branches/gcc-4_7-branch/libstdc++-v3/src/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/src/c++11/Makefile.am
    branches/gcc-4_7-branch/libstdc++-v3/src/c++11/Makefile.in
   
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-atomic-c++0x.cc
    branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-c++0x.cc
   
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-thread-c++0x.cc
    branches/gcc-4_7-branch/libstdc++-v3/src/c++98/Makefile.am
    branches/gcc-4_7-branch/libstdc++-v3/src/c++98/Makefile.in
    branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility-list-2.cc
    branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility.cc
    branches/gcc-4_7-branch/libstdc++-v3/testsuite/Makefile.in


  parent reply	other threads:[~2012-11-05 23:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28811-4@http.gcc.gnu.org/bugzilla/>
2011-04-28 16:41 ` rguenth at gcc dot gnu.org
2012-06-27 10:20 ` d.v.a at ngs dot ru
2012-06-27 10:28 ` d.v.a at ngs dot ru
2012-09-20  2:11 ` bkoz at gcc dot gnu.org
2012-11-05 23:42 ` bkoz at gcc dot gnu.org [this message]
2012-11-05 23:43 ` bkoz at gcc dot gnu.org
2013-11-15 15:15 ` paolo.carlini at oracle dot com
2006-08-22 20:29 [Bug libstdc++/28811] New: undefined versioned symbol name _ZNKSt14basic_ifstreamIcSt11char_traitsIcEE7is_openEv@GLIBCXX_3.4 pluto at agmk dot net
2006-08-27  4:55 ` [Bug libstdc++/28811] --with-pic vs static libraries and libstdc++ pinskia at gcc dot gnu dot org
2006-09-08 12:48 ` pluto at agmk dot net
2007-09-07  5:58 ` cnstar9988 at gmail dot com
2008-06-06 11:57 ` paolo dot carlini at oracle dot com
2008-06-06 12:02 ` paolo dot carlini at oracle dot com
2008-06-06 12:15 ` jakub at gcc dot gnu dot org
2008-06-06 13:27 ` hjl dot tools at gmail dot com
2008-06-08 15:45 ` hjl dot tools at gmail dot com
2008-11-14  0:33 ` pluto at agmk dot net
2009-01-28  1:41 ` bkoz at gcc dot gnu dot org
2009-01-28  3:25 ` bkoz at gcc dot gnu dot org
2009-08-04 12:34 ` rguenth at gcc dot gnu dot org
2010-05-22 18:17 ` rguenth at gcc dot gnu dot 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-28811-4-HVz7jRY7YR@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).