Subj : Re: __turboFloat problem To : borland.public.cpp.borlandcpp From : "Ed Mulroy [TeamB]" Date : Tue Sep 09 2003 06:14 pm One thing I see is that the startup code must be first in the list of object files. Discard the DLL's you've built, change the order of object files and build new DLL's. You haven't showed the command lines used to compile so it is not possible to know if it must be static (cw32mt) or dynamic (cw32mti) linked. Under BCB 6 both of those libraries have the public symbol __turboFloat but I do not have Borland C++ loaded on this machine so cannot check for that compiler. .. Ed > Martin Schneider wrote in message > news:bjl0vf$keb5c$1@ID-119488.news.uni-berlin.de... > > I created a project to build a DLL (actually a python extension) > on one machine, linking > > ilink32 -Tpd example c0d32,example.pyd,,mypylib import32 > cw32mt,example > > Everything works fine. Now I transferred the project to my laptop > and get an > "Unresolved external '__turboFloat'" > > error, which I can only solve by linking cw32mti instead of cw32mt. > Same compiler version, same libraries. Can anybody explain this > please? .