On 2009-Oct-16 13:05:02 +0100, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: >I'm updating a configure script which will warn users if their operating >system >is too old. In the case of a Solaris 9 machine it will say:
Whilst I agree in principal, I have some concerns about the wording. >configure: WARNING: You are using Solaris 9, which is a very old version >configure: WARNING: last released in 2004. Solaris 10 was first released in >configure: WARNING: 2005, and there have been many updates since then. You >configure: WARNING: are advised to upgrade to Solaris 10 or later, This is all very nice in principal but may not be possible in practice due to requirements for other applications. Eg, we still have a Solaris 2.6 server to support an old application. Whilst the application might work with Solaris 10, that would require effort to upgrade the OS and then regression test the application - for which there is no funding. I suspect you will find that Solaris 9 is still in fairly common use. Whether it's used widely enough to justify a Sage release, I'm not certain. (And I'm not certain how much effort would be needed to build Sage on Solaris 9). >configure: WARNING: not supported on Solaris 9, though it may work (the Sage Actually, you can be fairly confident it won't work because the libm version was bumped between Solaris 9 and Solaris 10 so you will get a "libm.so.2 not found" error fairly quickly. I would prefer a warning along the lines of: configure: ERROR: Sage is currently only supported on Solaris 10 and you configure: ERROR: are running an earlier version of Solaris. If you wish configure: ERROR: to assist in porting Sage to Solaris 9, please join the configure: ERROR: mailing list sage-devel@googlegroups.com BTW, the various Solaris 10 upgrades make fairly radical changes to the environment and I assume the build machines are running a fairly recent version of Solaris 10. Has anyone tried running the Solarris package on a early Solaris 10? It's possible there may be problems. >I think I'll have to leave any tests for linux (or let someone else >write them), as I believe there are too many different distributions >to worry about. It would be nice to have a list of base OS shared libraries that Sage expects and do a check against the available libraries. I'm not sure how much effort this would be. -- Peter Jeremy
pgppiGsEszJTH.pgp
Description: PGP signature
