|
From: Jim C. <li...@yg...> - 2003-05-05 02:44:02
|
Hi - I have a bit more information regarding the C++ related undefined symbols. The symbol names that show up as undefined match exactly those in OS X's libstdc++. So it looks like it is an issue of things not being found, rather than anything that is truly missing. Additionally, I discovered that setting the DYLD_INSERT_LIBRARIES environment variable to the full path to libstdc++.dylib before running an ht://Dig program seems to solve the problem of undefined symbols. This variable is used to specify dynamic libraries that should be loaded before any specified directly by a program. I think it is primarily intended for testing, but it does seem to identify the nature of the problem. Apparently the current build system somehow fails to record a libstdc++.dylib dependency, resulting the library not being loaded at runtime. All of the above holds regardless of the version of libtool used. Or at least for the current version and 1.5. Jim |