From: "J. Scott Edwards" <sedwards@xmission.com>
To: gcc@gcc.gnu.org
Subject: gxx_personality_v0 undefined - 2.96 Libraries 3.2 GCC
Date: Thu, 30 Jan 2003 20:21:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.53.0301301123240.15310@xmission.xmission.com> (raw)
I just switched this machine from Debian Woody to SuSE 8.1 GNU/Linux but
now when I try to build the software I'm working on I get this:
undefined reference to `__gxx_personality_v0'
in the .o files that come from .cpp files (the .c files don't seem to
have this problem).
I searched around and the only references I could find to
gxx_personality_v0 being undefined talk about using a 1.4.x libtool. I
checked and indeed this SuSE version has libtool 1.4.2.
I don't understand how all this fits together. I'm not even sure if I can
make this work. SuSE has GCC 3.2 but the (.a) libraries that I have were
compiled with 2.96. I don't have the sources to the libraries and I'm not
sure if I can get newer versions right now. I had hoped that the 2.96
libraries would work with 3.2 because they are not C++.
Is it possible to make this work or do I need to go back to an older
version of GNU/Linux that has an older compiler?
Thanks
-Scott
next reply other threads:[~2003-01-30 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 20:21 J. Scott Edwards [this message]
2003-01-31 4:12 ` Joe Buck
2003-01-31 19:22 ` J. Scott Edwards
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=Pine.GSO.4.53.0301301123240.15310@xmission.xmission.com \
--to=sedwards@xmission.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).