https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40411
Norm Jacobs <norm.jacobs at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |norm.jacobs at oracle dot com --- Comment #29 from Norm Jacobs <norm.jacobs at oracle dot com> --- Created attachment 38948 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38948&action=edit proposed fix to link values-*.o Unfortunately, due to the way support for behavioral differences in conflicting standards interfaces is implemented in Solaris libc and libm, there really isn't a perfect answer here. An offline discussion of this led to the conclusion that "the application dictates the xpg'ness and any library that thinks it has control from the compilation options it uses, is fooling itself." The current builds of GCC that are delivered with Solaris 11 and later include a patch very similar to the one that I have attached. The one that I have attached should only link in appropriate values-*.o files when GCC calls the linker to generate an executable program. This seems consistent with what the Studio compilers do.