Prototypes are not found with Studio 12.1?

Question

Hi all,
I try to compile a rather largish project, and I face a problem with the newest (Studio 12.1) compilers.
For example I get:
"/ufsbckp/head-64-slicer/64-cc/Slicer3/Libs/ModuleDescriptionParser/ModuleProcessInformation.h", line 40: Error: The function "strcpy" must have a prototype.
"/ufsbckp/head-64-slicer/64-cc/Slicer3/Libs/ModuleDescriptionParser/ModuleDescriptionParser.cxx", line 185: Error: The function "strcmp" must have a prototype.
[...]whereas <cstring>is included.
[ModuleProcessInformation.h|http://viewvc.slicer.org/viewcvs.cgi/trunk/Libs/ModuleDescriptionParser/ModuleProcessInformation.h?rev=7251&view=markup]
This is really just one example, as there were numerous similar errors during the compilation of BatchMake (www.batchmake.org - this is a dependency of Slicer).
I fixed them by adding the <string.h> include directive. I had similar errors with <cmath>, I had to add <math.h> for cos, sin because I got errors like Error: The function "sin" must have a prototype.A man <strlen; strcpy; sin...> reveals that the includes should be okay, I shouldn't need to add their .h counterparts.
I have never had similar problems with Studio 12.
Could somebody please guide me to the right direction on what's going on here?
I think that adding - seemingly superfluous - headers is just not right.
Yet another, but a little different question:
What can lead to similar warning messages?
Linking CXX shared library ../../bin/libFreeSurfer.so
ld: warning: symbol `std::codecvt<wchar_t,char,__mbstate_t>::__vtbl' has differing sizes:
     (file /opt/SUNWspro/lib/amd64/libCstd.so value=0x60; file /opt/SUNWspro/lib/stlport4/amd64/libstlport.so value=0x50);
     /opt/SUNWspro/lib/amd64/libCstd.so definition taken
ld: warning: symbol `std::time_put_byname<wchar_t,std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t> > >::__vtbl' has differing sizes:
     (file /opt/SUNWspro/lib/amd64/libCstd.so value=0x30; file /opt/SUNWspro/lib/stlport4/amd64/libstlport.so value=0x20);
     /opt/SUNWspro/lib/amd64/libCstd.so definition taken
ld: warning: symbol `std::numpunct<wchar_t>::__vtbl' has differing sizes:
     (file /opt/SUNWspro/lib/amd64/libCstd.so value=0x50; file /opt/SUNWspro/lib/stlport4/amd64/libstlport.so value=0x40);
     /opt/SUNWspro/lib/amd64/libCstd.so definition taken
ld: warning: symbol `std::cin' has differing sizes:
     (file /opt/SUNWspro/lib/amd64/libCstd.so value=0x90; file /opt/SUNWspro/lib/stlport4/amd64/libstlport.so value=0xc0);
     /opt/SUNWspro/lib/amd64/libCstd.so definition taken
ld: warning: symbol `std::messages<char>::__vtbl' has differing sizes:
     (file /opt/SUNWspro/lib/amd64/libCstd.so value=0x40; file /opt/SUNWspro/lib/stlport4/amd64/libstlport.so value=0x30);
     /opt/SUNWspro/lib/amd64/libCstd.so definition taken
[...]Theoretically we don't compile with stlport. (no -library=stlport4 flags)
Thank you all for taking the time to read or/and :) answer it!

Answer 1

marc1842fr wrote:
cstring gives you std::strcpy, string.h gives you ::strcpy (and std::strcpy, but you'd better not rely on that). Note that the typical gcc/glibc gets this wrong, so a lot of code is broken.Aha, so it's no news - only for me (I forgot to mention that - well, I won't call myself a programmer. Really, I mean - I'm a biologist. I just happen to like computers :))
>
Where did you find a man page that says cstring provides strcpy in the global namespace?Okay, I might have misunderstood those man pages. That's why I wrote "should" - in my interpretation. It seems it shouldn't.
That's okay, as the code can be fixed, the developers are helpful, and react really quickly.
>
Strange.Yes, it is. I used Studio 12 eversince it appeared. There were other problems compiling this software (I mean with Sun's compilers), but these I have now, haven't been there until now. To be honest, last time I tried to compile Slicer with Sun CC was months ago, so the code might have changed too.
>
Are you sure? Can't the program you are compiling have added it itself?And indeed: yes, they've added this flag. It' seems they've made it a default; it's new to me.
Then again: what about those warnings? Can they safely be omitted?
Thanks for the reply!
Edited by: -aspirin- on Aug 8, 2009 7:49 PM