public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Snopek <xevol@execpc.com>
To: gcc-help@gcc.gnu.org
Subject: Shared Libraries
Date: Sat, 08 Jul 2000 11:10:00 -0000	[thread overview]
Message-ID: <39676DEB.985DF973@execpc.com> (raw)

I have been working on a project that involves two shared libraries
being statically loaded by a binary file.  All the objects in the shared
library were compiled using the -fPIC and linked with -shared.  Then in
linking the binary, I just used the full path and name of the shared
libraries as argument.  As far as I know this is standard proceedure but
I am not sure because I picked it up from example.  Suddenly, three days
ago, I tryed to recompile all of my source including the libraries, and
when I got to linking the binary it gave me these three errors for every
class that is referenced in the shared libraries:
    undefined reference to class_name virtual table
    undefined reference to class_name type_info function
    undefined reference to class_name type_info node
The strangest part is that I didn't change anything in the shared
libraries, and made minimal changes to the binary (which I undid in
hopes of maybe getting it to work again).  I am using RedHat 6.1 on a
i386, all the source is in C++.  I would appreciate any help that any
one can provide!!

    - David Snopek


             reply	other threads:[~2000-07-08 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-08 11:10 David Snopek [this message]
2000-07-08 15:02 ` Martin v. Loewis
2000-07-08 16:16   ` David Snopek
2000-07-08 16:26     ` Kayvan A. Sylvan
2000-07-09  0:15     ` Martin v. Loewis
  -- strict thread matches above, loose matches on Subject: below --
1999-12-30  6:56 Shared libraries Coleman Baker
1999-12-31 22:24 ` Coleman Baker

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=39676DEB.985DF973@execpc.com \
    --to=xevol@execpc.com \
    --cc=gcc-help@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).