"Could not find a match" error when passing parameter prefixed with "std::"

Question

We're moving from Solaris 8 to Solaris 10, and I'm compiling our C/C++ applications using the Sun Studio 8 C++ compiler to verify that they'll still run correctly under Solaris 10.
All is well except for an error I'm getting on my Solaris 10 system but not on my Solaris 8 system.
Specifically, this line of code compiles correctly on both systems:
    if ( std::find_if(ident.begin(), ident.end(), is_not_alnum) != ident.end() )
        throw invalid_ident(caption, ident, code);but this line produces an error on Solaris 10 (but not on a Solaris 8 server):
    if ( std::find_if(ident.begin(), ident.end(), std::islower) != ident.end() )
        throw invalid_ident(caption, ident, code);The error returned is:
"auth_validate.C", line 140: Error: Could not find a match for std::find_if<std::InputIterator,
std::Predicate>(const char*, const char*, extern "C" int(int)).Clearly the "std::" prefix is involved... but why would this code compile successfully under Solaris 8 but fail under Solaris 10?
I've eliminated the usual suspects: the compiler is the same (including the include files) on both servers; there are no differences in the makefiles; there are no differences in the source code; all the referenced include directories exist on the Solaris 10 server.
At this point I'm stumped. My guess is that there's some environmental variable somewhere in Solaris 10 that is telling the Sun Studio 8 compiler to behave in a particular way (which Solaris 8 isn't telling the compiler), but I can't guess where such a thing might be occurring or what it might look like.
I've tried changing the source code to simply delete the "std::" prefix, and that code then compiles correctly on both my Solaris 8 and Solaris 10 servers. However, I'd very much prefer not to have to change any source code -- if this is an environmental issue with Solaris 10 affecting how the Sun Studio 8 C++ compiler behaves, I'd like to know about that.
If anyone can shed some light on this problem, or even propose additional tests I might try, I'd appreciate it!

Answer 1

clamage45, thanks very much for the response.
I'm looking into putting together a small example app. Meanwhile, I took your suggestion to check the patch levels of the two compiler instances and lo! there is a discrepancy.
The compiler installed on our Solaris 8 server reports itself from a CC -V command as "CC: Sun C++ 5.5 Patch 113817-19 2006/10/13", while the version on the Solaris 10 server reports as "CC: Sun C++ 5.5 2003/03/12". So although my eyeball comparison of the compiler's include files and libraries (including file sizes and timestamps) showed no differences, that was just a spot check; it wasn't the more "official" check that you helpfully suggested.
I've asked our sysadmin to look into this. No guarantees, of course, but I would not be surprised if patching the compiler on our Solaris 10 system resolved the problem. (Assuming we can find a version of the most recent patch for the Sun Studio 8 C++ compiler that's valid for Solaris 10.)
Regarding Sun Studio 8, we're definitely aware that it's reached its expiration date. We already have plans to transition to a more up-to-date version (probably Sun Studio 12) at a later date -- all I'm doing currently is testing to verify that the current application compiles and runs properly on Solaris 10. If possible, I'd like to get that working independently of any potential code changes driven by a significant compiler version upgrade.
Thanks again, and I'll add a new comment with additional information if our patching doesn't help.