Tim Mooney wrote:
> If you're going to try 4.x, try 4.4.9.  It should be much easier to build
> on Solaris 8 than all previous versions of 4.x..., You should probably go
> with 5.0.x, though. 
...
> I used the free Sun Workshop compiler rather than gcc
...
> I have 4.4.9 built and working on Solaris 8.
> 
> Post what problems you're running into, I'll try help as time permits.
> 
> Tim

Thanks a lot, Tim!  :)  I really appreciate a little assistance.

BTW, I'm at UTC +2, so we're working on different timeframes.... (I'm 
answering this from home, so you'll see it the same day, and hopefully 
I'll have an answer for my morning.)

I had kind of given up on 4.3.3, and started with 5.0.3 because I 
concluded that the rewrite had cleaned up a lot of dependencies and 
cleared out cruft, so that I hoped for an easier build.  Unfortunately, 
I'm a ways down the GCC path with that.

First BIG question:
Do you think I'm better off
- starting over with 4.4.9 an Sun's cc, as you've done,
- keep going with 5.0.3 but restart on cc,
- or just to keep plugging with 5.0.3 on gcc?

Background:
We have a large Solaris code base being forked to Linux.  The Linux team 
has no packaging tool yet, and part of the Solaris team has been using 
Solaris packages, but most groups just use tarballs and homegrown shell 
scripts.  I'm the one who has to select a tool for everyone to converge 
on, then build some templates, write some docs, and give some training 
to get everyone up to speed.

Risk Analysis:
I'm over schedule right now, and I need to give a report to my manager 
tomorrow about which way we're going to go.  (Dropping RPM is another 
option, but that entails a whole different set of risks.)

4.4.9 would best keep us in sync with the CentOS version 4.3.3 that 
another team member has started playing with, and should be most 
interoperable in terms of of .spec files.

5.0.3 would position us for the future, but require upgrading the Linux 
work, too, and building a tool suite for the Linux team as well as the 
Solaris team.

Continuing with gcc has no great advantage at present, but it might help 
the Solaris team slowly switch over to gcc if they benefited from new 
libraries and stuff that I have to build.  The guy running the unified 
cmake project would like that, anyway. :)  And I can sell it to my 
manager as reducing divergence across the OS fork in the future.

Going with cc would keep the Solaris people happy.


So what do you think?


-    Eliyahu

-- 
Eliyahu Skoczylas <EliSko@Eli-Sko.com>  New phone! +972 (54) 214-1505
GPG public key online at <http://www.Eli-Sko.com/keys/EliSko1.gpgkey>
GnuPG fingerprint: BFE4 7F12 4B97 157D 5226  A527 325D ED87 07BC EC60