Re: Linker error with purify
Is the error a general linker error, or is it a purify error?
If it is a linker error, then the obvious first step is to see if the library where the C++ standard library exists is seen by the linker. How you do that within CC or that "purify" command-line is something you need to investigate.
More than likely, the linker settings are wrapped up in CC while they are incomplete or missing in the "purify" command.
Regards,
Paul McKenzie
Re: Linker error with purify
I'm actually having a similar trouble in Visual Studio.....release build works fine, but when I switch to debug I get a mysterious unresolved external symbol error that I really shouldn't be getting. It's the constructor for one of my classes. I'm looking right at it, I know it exists, even release mode knows it exists. But debug doesn't.....
If I figure out what's going on I'll let you know, although I doubt it's exactly the same problem.
Re: Linker error with purify
Thanks for your responses but I think I figured out what the problem was. I don't know why it appears to be doing this, but it looks like it's completely ignoring the LD_LIBRARY_PATH environment variable. So, the location of the standard C++ libraries were not being seen. If I force the paths to these libraries by using the -L and -R options on the compiler command line, then it actually works. Of course, this doesn't explain why I don't get the linker error in non-debug mode without having to force the paths.