public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Fred Richardson <frichard@bbn.com>
To: egcs@cygnus.com
Subject: More on {multiple,un}-defined symbols with egcs-971207
Date: Sat, 13 Dec 1997 13:49:00 -0000	[thread overview]
Message-ID: <199712132149.QAA21596@bluebell.bbn.com> (raw)

Well, I got rid of the undefined symbols by removing the old shared
library and linking staticly to the new library (I thought I was doing
this by default ala --disable-shared).

But the multiple definition error for
    __default_alloc_template...::free_list 
are still there.  Does anyone know of a way to get rid of these?  It
looks like they're genertaded by the stl header files:

  obj.sun4sol/Traceback.od:/d4mutl/contrib/egcs/include/g++/stl_vector.h:350: multiple definition of `__default_alloc_template<false, 0>::free_list'
  obj.sun4sol/NBest.od:/d4mutl/contrib/egcs/include/g++/stl_tree.h:271: first defined here
  obj.sun4sol/PdfCbkMap.od:/d4mutl/contrib/egcs/include/g++/stl_alloc.h:409: multiple definition of `__default_alloc_template<false, 0>::free_list'
  obj.sun4sol/NBest.od:/d4mutl/contrib/egcs/include/g++/stl_tree.h:271: first defined here

Again, thanks in advacne for any help with this stuff, 

                 -Fred


                 reply	other threads:[~1997-12-13 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199712132149.QAA21596@bluebell.bbn.com \
    --to=frichard@bbn.com \
    --cc=egcs@cygnus.com \
    /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).