public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Butcher <paul.butcher@asa.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Problem with C++ on gcc 3
Date: Thu, 04 Jul 2002 02:18:00 -0000	[thread overview]
Message-ID: <E17Q2gR-0002tI-00@bentley.asa.co.uk> (raw)

I have a rather basic problem with compiling a simple C++ program, or rather 
with the final linking using collect2.  This is the call made:
/opt/experimental/bin/gcc -v -O2 -o CPPTest ../CPPTest.cpp ../CPPTestMain.cpp

The following is the verbose output for the final collect2 stage:
 /opt/experimental/lib/gcc-lib/i486-suse-linux/3.0.1/collect2 -m elf_i386 
-dynamic-linker /lib/ld-linux.so.2 -o CPPTest /usr/lib/crt1.o /usr/lib/crti.o 
/opt/experimental/lib/gcc-lib/i486-suse-linux/3.0.1/crtbegin.o 
-L/opt/experimental/lib/gcc-lib/i486-suse-linux/3.0.1 
-L/opt/experimental/lib/gcc-lib/i486-suse-linux/3.0.1/../../.. 
/tmp/cc3xAK5D.o /tmp/ccq0irtE.o -lgcc -lc -lgcc 
/opt/experimental/lib/gcc-lib/i486-suse-linux/3.0.1/crtend.o /usr/lib/crtn.o
/tmp/ccq0irtE.o: In function `__FRAME_BEGIN__':
/tmp/ccq0irtE.o(.eh_frame+0x12): undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status

As you see this is with SuSE7.3 LInux gcc 3.0.1 'experimental' build - but I 
get the same problem with a cygwin compiled gcc 3.1 on Win9X. 
The problem occurs with the most minimal C++ class so I presume it's 
something fundamental I'm doing wrong!

(It always worked with gcc 2.95.x)

Paul Butcher
ALTON, Hants, UK

             reply	other threads:[~2002-07-04  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04  2:18 Paul Butcher [this message]
2002-07-04  3:39 ` Andrea 'Fyre Wyzard' Bocci
2002-07-08  1:54   ` Paul Butcher
2002-07-08  8:03     ` Andrea 'Fyre Wyzard' Bocci
2002-07-09  1:09       ` Paul Butcher

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=E17Q2gR-0002tI-00@bentley.asa.co.uk \
    --to=paul.butcher@asa.co.uk \
    --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).