SPARC Solaris 10?

[Jeff A. Earickson]

On Sun, 7 May 2006, Julian Field wrote:
>> 
>> Did you remember about perlgcc?
>> 
>> [mgt at hypernova ~]$ which perlgcc
>> /usr/perl5/bin/perlgcc
>> [mgt at hypernova ~]$ uname -a
>> SunOS hypernova 5.10 Generic_118833-03 sun4u sparc SUNW,UltraAX-i2
>> 
>> Without it all perl modules will look for the Sun Compiler.
>> 
>
> I have just ripped apart my install.tar-fns.sh script and it's started to 
> work!
> Yay, and thanks to whoever it was who pointed me towards SUNWspro. I didn't 
> realise it was free these days :-)

No problem.  I don't know why they don't just make SUNWspro part of S10
now that its free.  FWIW, I don't use Sun's version of perl.  I build
and install the public-domain version, and make sure that it is /usr/bin/perl.
I specifically delete the SUNWCperl cluster in my jumpstart setup for
Solaris 10.  In fact, I delete a lot of clusters and packages in my
default S10 install, such as GNOME, apache, perl, sendmail, mozilla, etc.
It makes the install footprint much smaller and still gives me all of the
server functionality I want.

If I want things like sendmail or perl, I build and install the public-domain
versions.  Then I *know* what compiler and options got used and how they got 
there.  More work up front but less guessing and hassle later on.

I also build nearly all critical software items with SUNWspro.  While GCC
is a great compiler, I've sometimes had problems with GCC apps and Sun
shared libs -- problems I don't have with SUNWspro.  But some things won't
build cleanly with SUNWspro, so GCC remains available.

Jeff Earickson
Colby College