From: prj@po.cwru.edu (Paul Jarc)
To: "VallabhaN" <VallabhaN@bristol.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Linker Errors
Date: Mon, 12 Aug 2002 09:18:00 -0000 [thread overview]
Message-ID: <m3ofc8nj3x.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <85256C13.001FCF6E.00@bristolhq.bristol.com> ("VallabhaN"'s message of "Mon, 12 Aug 2002 11:10:41 +0530")
"VallabhaN" <VallabhaN@bristol.com> wrote:
> /home/libcommdlg44.so: undefined reference to `__pure_virtual'
> /home/libcommdlg44.so: undefined reference to `__rtti_user'
> /home/libcommdlg44.so: undefined reference to `__rtti_si'
> /home/libcommdlg44.so: undefined reference to `__throw'
> /home/libcommdlg44.so: undefined reference to `terminate(void)'
> /home/libcommdlg44.so: undefined reference to `__rtti_class'
These are C++ facilities; make sure you're using g++ to link, not gcc.
paul
next prev parent reply other threads:[~2002-08-12 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 22:51 VallabhaN
2002-08-12 9:18 ` Paul Jarc [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-20 14:31 Linker errors Larry
2001-02-13 15:11 yarrakonda srinivasa reddy
2001-02-14 16:57 ` Alexandre Oliva
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=m3ofc8nj3x.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=VallabhaN@bristol.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).