How to compile a glibc without c++ exception handling?

Ichiro Barnes
Thu Jun 26 18:53:00 GMT 2003


I am building a i386 linux/arm linux cross compilation
environment, but my dynamically linked executables
fail to run on the target due to undefined symbols
such as 'register_frame_info'.

I understand that the cause of this is that the glibc
I built is inserting references to c++ exception
handling routines in my c code, but that the glibc
running on my target wasn't built with those symbols

Now for what is no doubt a blazingly newbie question:
how can I build a glibc that doesn't insert those

I am building glibc 2.3 using gcc 3.2.2. I did see
this topic addressed in the glibc FAQ, but didn't see
any advice for the version I'm working with. To set up
my cross compilation environment, I followed the
instructions in

Thank you in advance for your advice.


Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

More information about the Gcc-help mailing list