CODEWITHSUNDEEP
c++visual-studio-2010visual-age
karthik kumar
karthik kumar

Reputation: 1

Migration from IBM VisualAge C++ 3.6.5 to VS 2010

We're in the process of migrating 32-bit C++ application to 64-bit application (VS 2010). This application was developed 10 years back with IBM VisualAge C++ 3.6.5 for Windows. Since IBM has stopped support of this compiler, we're facing issues while migrating it to VS 2010.

This is mostly because of some missing libraries.

Sample errors:

error LNK2019: unresolved external symbol __uopen referenced in function "int __cdecl allocate_heap_storage_(void)" (?allocate_heap_storage@@YAHXZ) error LNK2019: unresolved external symbol __ucreate referenced in function "int __cdecl allocate_heap_storage_(void)" (?allocate_heap_storage@@YAHXZ) error LNK2019: unresolved external symbol __udestory referenced in function "int __cdecl deallocate_heap_storage_(void)" (?deallocate_heap_storage@@YAHXXZ) error LNK2019: unresolved external symbol __uclose referenced in function "int __cdecl deallocate_heap_storage_(void)" (?deallocate_heap_storage@@YAHXXZ) error LNK2019: unresolved external symbol __umalloc referenced in function "int __cdecl alloc_share_mem_(int,int)" (?alloc_share_mem@YAPAXHH@Z)

The above functions are defined in umalloc.h but we are missing the definitions.

How can we resolve this?

Upvotes: 0

Views: 426

Answers (1)

Matt
Matt

Reputation: 6050

For the errors above, these function "_ucreate",_udestory , _uclose,_umalloc" are not found when linking, I think these functions were in the run time libraries provided by Visual Age. if you can find the lib files of the these run time libraries, you can put them in the input of link, it may pass the compiling phase, but may fail to launch.

One suggestion here is to replace the functions above with windows functions. All the functions above are related with memory allocations.

Upvotes: 0

Related Questions