Vtable error while using RVCT3 | developer.brewmp.com Vtable error while using RVCT3 | developer.brewmp.com

Developer

Vtable error while using RVCT3

I compile everything just fine..... but when it goes to link I get this:

Error: L6218E: Undefined symbol vtable for __cxxabiv1::__si_class_type_info (referred from A.arm.o).
Error: L6218E: Undefined symbol vtable for __cxxabiv1::__class_type_info (referred from B.arm.o).
Error: L6218E: Undefined symbol __aeabi_uidivmod (referred from B.arm.o).
Error: L6218E: Undefined symbol vtable for __cxxabiv1::__vmi_class_type_info (referred from Game.arm.o).
Error: L6218E: Undefined symbol __aeabi_atexit (referred from Game.arm.o).
Error: L6218E: Undefined symbol __aeabi_idivmod (referred from Game.arm.o).
Error: L6218E: Undefined symbol __aeabi_vec_delete (referred from Game.arm.o).
Error: L6218E: Undefined symbol __aeabi_vec_new_cookie (referred from Game.arm.o).
Error: L6218E: Undefined symbol __dso_handle (referred from Game.arm.o).
Error: L6218E: Undefined symbol abort (referred from Game.arm.o).
Error: L6218E: Undefined symbol __cpp_initialize__aeabi_ (referred from anon$$obj.o).

Does anyone know what the problem is?

vtable .. sounds like you used virtual function in the class.
As to the others is it possbile that you didn't use extern "C" in the header file for c code? --just guess

vtable .. sounds like you used virtual function in the class.
As to the others is it possbile that you didn't use extern "C" in the header file for c code? --just guess

Yup lots of virtuals.... but those SHOULD be supported correctly (heck they worked in ADS1.2)
Not sure about the C extern stuff either... we're trying to upgrade from ADS 1.2 to RVCT 3 and we're having these issues.

Yup lots of virtuals.... but those SHOULD be supported correctly (heck they worked in ADS1.2)
Not sure about the C extern stuff either... we're trying to upgrade from ADS 1.2 to RVCT 3 and we're having these issues.

I guess there's something wrong with c++ ABI which the RVCT3.0 use.
Have a check at:
http://brewforums.qualcomm.com/showthread.php?t=16071
Hope you can get some clue

I guess there's something wrong with c++ ABI which the RVCT3.0 use.
Have a check at:
http://brewforums.qualcomm.com/showthread.php?t=16071
Hope you can get some clue

BUMPING. We still haven't been able to get past this and nothing on the other thread has been very helpful. What are the proper linking options as well as compilation options? We probably do not have the right ones. But I haven't seen anything in the options that would relate to messed up vtable stuff as you see in my OP

BUMPING. We still haven't been able to get past this and nothing on the other thread has been very helpful. What are the proper linking options as well as compilation options? We probably do not have the right ones. But I haven't seen anything in the options that would relate to messed up vtable stuff as you see in my OP

My linkline in my test project has
armlink --libpath C:\Apps\ARM\RVCT30\RVCT\Data\3.0\651\lib ...
If I remove the libpath, I get the first three errors you mention. I wouldn't expect to get the rest in my project.

My linkline in my test project has
armlink --libpath C:\Apps\ARM\RVCT30\RVCT\Data\3.0\651\lib ...
If I remove the libpath, I get the first three errors you mention. I wouldn't expect to get the rest in my project.