This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: Exceptions
- To: libstdc++ at sourceware dot cygnus dot com
- Subject: Re: Exceptions
- From: Chris Prince <prince at wcug dot wwu dot edu>
- Date: Wed, 29 Sep 1999 10:13:57 -0700 (PDT)
- cc: Benjamin Kosnik <bkoz at cygnus dot com>
Thanks to Benjamin, I (we) have solved the issue that I was having below.
One must be very careful to make sure that when compiling you are using
the correct compiler. I apparently had a version of egcs-2.90.66 sitting
in my /usr/bin directory. However, in doing a which I believed I was
using gcc in my /usr/local/bin. So when I did a command line compile
everthing worked like a charm, but when I used my Makefile it defaulted to
/usr/bin thus using the wrong compiler and causing a number of problems.
So the moral of the story is? Got milk?
Thanks Benjamin.
On Tue, 28 Sep 1999, Benjamin Kosnik wrote:
>
> > `basic_ostream<wchar_t, char_traits<wchar_t> >::operator<<(basic_ios<wchar_t, char_traits<wchar_t> > &(*)(basic_ios<wchar_t, char_traits<wchar_t> > &))':
> > /home/chrisp/compiler/bld-libstdc++/src/../../libstdc++-2.90.6.1/bits/std_ostream.h:116: undefined reference to `__eh_rtime_match'
> > /home/chrisp/compiler/bld-libstdc++/src/../../libstdc++-2.90.6.1/bits/std_ostream.h:116: undefined reference to `__start_cp_handler'
> > /usr/local/lib/libstdc++.a(misc-inst.o): In function `basic_ostream<wchar_t, char_traits<wchar_t> >::operator<<(ios_base &(*)(ios_base &))': /home/chrisp/compiler/bld-libstdc++/src/../../libstdc++-2.90.6.1/bits/std_ostream.h:136: undefined reference to `__eh_rtime_match'
> > /home/chrisp/compiler/bld-libstdc++/src/../../libstdc++-2.90.6.1/bits/std_ostream.h:136: undefined reference to `__start_cp_handler'
>
> My gcc-2.95.1 build directory has a libgcc.a with the following:
>
> % nm libgcc.a -A | grep __eh_rtime_match
> libgcc.a:_eh.o:000003dc T __eh_rtime_match
> % nm libgcc.a -A | grep __start_cp_handler
> libgcc.a:exception.o:00000100 T __start_cp_handler
>
> Sounds like you are linking against the wrong version of libgcc.a -- you
> should check your paths and make sure that when you compile you are
> indeed using the libraries and headers that you expect. (g++ -v -H is
> useful for this purpose.)
>
> -Benjamin
>
Chris :)
prince@wcug.wwu.edu
===================
What is "Windows 95/98"?
32 bit extensions for a 16 bit patch to an 8 bit operating system
originally coded for a 4 bit microprocessor written by a 2 bit company
that can't stand 1 bit of competition