public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lionel.champalaune@sophia.inria.fr To: gcc-gnats@gcc.gnu.org Subject: c++/7518: Problem on opening a shared library with Gcc3.1.1 Date: Wed, 07 Aug 2002 00:36:00 -0000 [thread overview] Message-ID: <20020807072858.11507.qmail@sources.redhat.com> (raw) >Number: 7518 >Category: c++ >Synopsis: Problem on opening a shared library with Gcc3.1.1 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed Aug 07 00:36:04 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Lionel Champalaune >Release: GCC 3.1.1 >Organization: >Environment: i686-pc-linux >Description: An error message appear when a shared library is opened. > Error: ./libTestlib.so: undefined symbol: _ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1ESt13_Ios_Openmode This problem didn't appear with the 3.1 version. Libtool is used, and it's in the generated compilation that the bug appears. This problem doesn't appear when the -g option to gcc is given. By using g++ instead of gcc, the problem disappear. gcc is used by libtool in a looklike utilization. >How-To-Repeat: run the file Command: >./Commandgcc >Fix: Used g++ instead of gcc in the second line: >./Commandg++ >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="Commandgcc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Commandgcc" ZysrIC1jIC1vIFRlc3RsaWIubG8gVGVzdGxpYi5DIApnY2MgLXNoYXJlZCBUZXN0bGliLmxvIC1X bCwtc29uYW1lIC1XbCxsaWJUZXN0bGliLnNvIC1vIGxpYlRlc3RsaWIuc28KZysrIFRlc3RtYWlu LkMgLWxkbAouL2Eub3V0Cg==
next reply other threads:[~2002-08-07 7:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-07 0:36 lionel.champalaune [this message] 2002-08-07 0:46 Lionel Champalaune 2002-09-13 16:21 nathan
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=20020807072858.11507.qmail@sources.redhat.com \ --to=lionel.champalaune@sophia.inria.fr \ --cc=gcc-gnats@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: linkBe 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).