On Sun, Dec 02, 2007 at 11:51:18AM -0500, Kevin O'Connor wrote: > When I went through this exercise, I just started commenting out stuff > to see what was forcing the exceptions into the exe. I got down to > the following stuff still needed from libsupc++.a: > > undefined reference to `vtable for __cxxabiv1::__si_class_type_info' > undefined reference to `vtable for __cxxabiv1::__vmi_class_type_info' > undefined reference to `vtable for __cxxabiv1::__class_type_info' > undefined reference to `__cxa_pure_virtual' >
Okay, so the magic gcc flag here is: -fno-rtti With that I can finally get haret (heavily modified) to compile without the c++ baggage. (Unfortunately, haret does use rtti.) Jacek, I think it would be better to reword your FAQ so that it states using -fno-exceptions, -fno-rtti, and using gcc instead of g++. Anything less and even simple c++ programs are going to end up pulling in all the code. Even with these steps, it is likely stubs for new, delete, and __cxa_pure_virtual will be needed. Thanks. -Kevin ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
