public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: gcc@gcc.gnu.org
Subject: C++ Issue on GCC 3.0 branch
Date: Fri, 20 Apr 2001 09:47:00 -0000	[thread overview]
Message-ID: <4423.987784910@slagheap.cygnus.com> (raw)

A few of the remaining failures for PA32 using static libraries are
multiply defined symbols -- in each case one or more symbols defined by
the main program is a duplicate of a symbol in libstdc++.

For example, compiling g++.law/cvt2.C results in about a dozen duplicate
symbols (output has been massaged to be easier to read).

"std::istream::~istream()" in files cvt.o and libstdc++.a (misc-inst.o)

Similarly for the following symbols:

"std::basic_ios<char, std::char_traits<char> >::~basic_ios()"
"std::basic_ifstream<char, std::char_traits<char> >::~basic_ifstream()"
"std::basic_ios<char, std::char_traits<char> >::~basic_ios()"
"std::basic_ifstream<char, std::char_traits<char> >::basic_ifstream(char 
const*, std::_Ios_Openmode)"

[ ... ]

I'm not enough of a C++ guru to know where to start with this one, so any
help y'all could provide would be greatly appreciated.

jeff



             reply	other threads:[~2001-04-20  9:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  9:47 Jeffrey A Law [this message]
2001-04-20 21:29 John David Anglin
2001-04-20 21:31 ` David Edelsohn
2001-04-21 10:11 ` Mark Mitchell
2001-04-22 14:54   ` John David Anglin
2001-04-22 16:22     ` Mark Mitchell
2001-04-22 17:18       ` John David Anglin
2001-04-23  8:03         ` law
2001-04-23  8:29           ` John David Anglin
2001-05-06  9:33             ` law
2001-05-06  9:59               ` John David Anglin
2001-04-23  7:59     ` law
2001-04-23  8:08       ` John David Anglin
2001-04-23  8:19         ` law
2001-04-23  8:45           ` John David Anglin
2001-04-23 10:39           ` John David Anglin
     [not found] <20010421123809V.mitchell@codesourcery.com>
2001-04-21 16:05 ` John David Anglin
     [not found] <no.id>
2001-04-21 19:33 ` John David Anglin
2001-04-23  2:18   ` Bernd Schmidt
2001-04-23  7:51     ` law
2001-04-23  7:55       ` Bernd Schmidt
2001-04-23  7:56       ` Bernd Schmidt
2001-04-23  8:14         ` law
2001-04-25 10:26   ` Mark Mitchell
2001-04-25 14:04     ` John David Anglin
2001-04-25 17:31       ` Mark Mitchell
2001-04-26  8:31         ` John David Anglin
2001-04-26 10:25           ` Mark Mitchell
2001-04-26 10:02         ` law
2001-04-23 15:21 ` John David Anglin
2001-04-24 19:21   ` law
2001-04-24 20:23     ` John David Anglin
2001-04-26 16:45       ` law
2001-04-26 17:02         ` Mark Mitchell
2001-04-26 17:29           ` law
2001-04-27 10:43         ` John David Anglin
2001-04-27 15:14         ` John David Anglin
2001-04-28  9:55           ` law
2001-04-30  8:59         ` John David Anglin
2001-04-28 10:43 John David Anglin

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=4423.987784910@slagheap.cygnus.com \
    --to=law@cygnus.com \
    --cc=gcc@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).