While I agree with you in principle, we should be building all of
Solaris with Studio, there are cases where using Studio is not really
worth the effort. There are several open source components out there
that seem to make heavy use of GCC extensions or what I more "lovingly"
like to think of as gccisms. If we are largely just acting as a conduit
for delivering the component, it requires significant patching to build
with Studio, and the upstream community isn't interested in taking back
the change, Studio for the sake of building with Studio isn't really
worth the effort. It means potentially generating new patches for each
bug fix or update simply because we like Studio. In the case where
using something other than Studio is going to introduce compatibility
issues, I would agree, Studio is a requirement. g++ is an example of of
a tool with compatibility issues.
In the case of SWIG, it appears to already be being built using Studio
in the SFW gate for subversion's private use (I won't touch that for
now), so there is no reason to use GCC and no reason for the
SUNWgccruntime dependency. Worse yet, it would be using g++ and
introducing compatibility problems.
-Norm
Octave Orgeron wrote:
> Agreed. All software in the OS should be compiled with Sun Studio. The GNU
> stuff should just be there to help developers port things. Not to mention how
> poorly g++ performance is on Solaris, let alone SPARC.
>
>
> ----- Original Message ----
> From: Rainer Orth <ro at techfak.uni-bielefeld.de>
> To: Gary Winiger <gww at eng.sun.com>
> Cc: psarc-ext at sun.com; Bruce.Rothermal at sun.com
> Sent: Friday, August 1, 2008 8:15:00 AM
> Subject: Re: 2008/475 SWIG for Open Solaris
>
> Gary Winiger <gww at eng.sun.com> writes:
>
>
>> Dependencies
>> ============
>> SUNWgccruntime GCC Runtime libraries
>>
>
> Why the dependency on SUNWgccruntime? Is SWIG being built with g++? If
> so, this means that all C++ users of SWIG would be forced to use g++ as
> well due the incompatible ABIs vs. Sun Studio CC.
>
> Rainer
>
>
