This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Greetings, I am using crosstool 0.10 to build a 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 defined. Now for what is no doubt a blazingly newbie question: how can I build a glibc that doesn't insert those references? What am I doing wrong? Adding a -f no-exceptions doesn't seem to cure the problem. I am using gcc 3.2.3 and glibc 2.2.5. Thanks in advance for your help, -I __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |