Undefined symbols at run time for gcc-2.95.3

[David Korn]

>-----Original Message-----
>From: Ernest L. Williams Jr. [ mailto:ernesto@ornl.gov ]
>Sent: 30 October 2001 04:02


>Hi Dave,
>
>Still trying to use gcc-2.95.3 with vxWorks headers
>I get some undefined symbols under vxWorks:
>--------------------------------------------------------------
>Undefined symbol: __start_cp_handler (binding 1 type 0)
>Undefined symbol: __eh_rtime_match (binding 1 type 0)
>Undefined symbol: __eh_alloc (binding 1 type 0)
>value = 28671088 = 0x1b57c70
>---------------------------------------------------------------
>
>Dave, have you seen this behavior?  What am I missing in terms of 
>exception handling?

    Hi Ernest,


  You progably stil have -nostdlib in your build flags somewhere.  You
need to link with libgcc.a, which would be done automatically without
that flag.  Alternatively if you aren't actually using the C++ exception
system, you can save a whole load of executable file size and runtime
overhead by specifying -fno-exceptions.

   cheers,
     DaveK
-- 
Burn your ID card!  http://www.optional-identity.org.uk/
Help support the campaign, copy this into your .sig!


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com