[csw-maintainers] C++ hell with Sun Studio and GCC

Dagobert Michelsen dam at opencsw.org
Tue Sep 22 07:45:33 CEST 2009

Hi Ben,

Am 21.09.2009 um 19:11 schrieb Ben Walton:
> Excerpts from Dagobert Michelsen's message of Sat Sep 19 10:34:28  
> -0400 2009:
>> As Ruby is compiled with GCC I need to compile xapian with GCC
>> too, otherwise the mangling does not work. However, Python requires
>> Sun Studio. Is there any kind of "mangling conversion" between
>> Sun Studio and GCC or must I really provide two versions of the
>> xapian libraries?
> I think moving ruby to SOS12 is the better long term solution, but
> could this be handled with modulations?

Definitely. That would mean Ruby for Solaris 8 with GCC and starting
with Solaris 9 with Sun Studio 12? That would make things of additional
packages awfully hard as they would require modulations too. I like
deprecation of Solaris 8 better here due to the massive complexities
introduced with the splitted compilation. Anyway, an example for
a compiler modulation is libtool.

So I propose making a Solaris 8 Ruby with GCC if you really need it
and starting with Solaris 9 and Sun Studio 12 for eveything else.

BTW, are you interested in packaging up RubeEE and Phusion Passenger?
I would need that also for my project, but as Ruby maintainer this
would naturally be more on your side ;-)

Best regards

   -- Dago

More information about the maintainers mailing list