From: Nathan Sidwell <nathan@codesourcery.com>
To: sinisa@mysql.com
Cc: gcc@gcc.gnu.org
Subject: Re: __cxa_pure_virtual
Date: Fri, 30 Nov 2001 09:10:00 -0000 [thread overview]
Message-ID: <3C07BD2B.9BC71FAB@codesourcery.com> (raw)
Message-ID: <20011130091000.MD6rkPbEL3iRfjp-3WYcYg9mONEpGgyOqxhrBBFvlLQ@z> (raw)
In-Reply-To: <15367.40775.654107.915798@sinisa.nasamreza.org>
Sinisa Milivojevic wrote:
> Is there a way of compiling a C++ file, which does not contain any
> references to STL classes, so that resultant object file will have no
> references to the above symbol, defined in pure.cc of libstdc++.
Other than by providing definitions of all your abstract functions, no.
> Any solution or work-around ??
You can also link with libsupc++, which contains just the C++ runtime
support routines without the std lib stuff. Or you could define that
symbol explicitly to the linker
--defsym __cxa_pure_virtual=0
(or, if invoked via gcc)
-Wl,--defsym -Wl __cxa_pure_virtual=0
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next prev parent reply other threads:[~2001-11-30 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 23:54 __cxa_pure_virtual Sinisa Milivojevic
2001-11-23 2:59 ` Nathan Sidwell [this message]
2001-11-23 3:42 ` __cxa_pure_virtual Sinisa Milivojevic
2001-11-23 15:24 ` __cxa_pure_virtual Phil Edwards
2001-11-30 11:35 ` __cxa_pure_virtual Phil Edwards
2001-12-01 4:54 ` __cxa_pure_virtual Sinisa Milivojevic
2001-11-23 15:37 ` __cxa_pure_virtual Alexandre Oliva
2001-11-30 11:45 ` __cxa_pure_virtual Alexandre Oliva
2001-12-01 4:56 ` __cxa_pure_virtual Sinisa Milivojevic
2001-11-30 9:21 ` __cxa_pure_virtual Sinisa Milivojevic
2001-11-30 9:10 ` __cxa_pure_virtual Nathan Sidwell
2001-11-30 6:58 ` __cxa_pure_virtual Sinisa Milivojevic
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=3C07BD2B.9BC71FAB@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=sinisa@mysql.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).