>I'm not familiar with SuSE, but I woul;d guess that if binaries created
>on S7 run on S8 and RHL 7, then they should also run on RHL 8.
I am familliar with both SuSE and RH on multiple platforms, and that isn't
necessarilly true.
>However, I would not expect people to be running RHL 7.x or 8.x on
>mainframes, but rather RHLES variants. The principle holds though,
>expect compatibility libraries to be available to run binaries on more
>recent releases than they were built on.
Getting complex C++ binaries running and stable on all of: SLES-7, SLES-8 ,
RHAS 2.1 ,RHAS 3.0
without installing unsupported libraries is a non-starter for example.
There's no single common C++ runtime available, and the exception handling
model in the different runtimes is (lethally) incompatible.
Peter
John Summerfield
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
afe.com.au> cc:
Sent by: Linux on Subject: Re: Linux on 390 Port
390 Port
<[EMAIL PROTECTED]
T.EDU>
24/09/2003 07:11 PM
Please respond to
Linux on 390 Port
On Wed, 24 Sep 2003, Peter Waltenberg wrote:
> 1 - Do I need to be concerned about differences between Linux
> distributions?
> I.e. if I get it to work under SuSE will it work on RedHat or Debian
> assuming
> the kernel level is the same or compatible? Is the main difference in
the
> administration/maintenance utilities provided with the package?
>
> A bit more detail.
>
> Source is generally portable, though if it's heavyweight GUI code even
> there you can have problems.
>
> Binaries:
> Compiled C code is generally fairly portable across a wide range of
> distro's.
> Compiled C++ is less portable - though you can generally manage to get
> portability across one generation of distributions with careful choice of
> build platforms or up one level. i.e. You can usually run on Suse 7 and
> RedHat 7 if you compiled on Suse 7, or Suse 8 if you compiled on Suse 7,
or
> RedHat 8 if you compiled on RedHat 8. The odds are getting the same
> binaries of compiled C++ to install and run on all of Suse 7, RedHat 7,
> Suse 8 and RedHat 8 are pretty small.
I'm not familiar with SuSE, but I woul;d guess that if binaries created
on S7 run on S8 and RHL 7, then they should also run on RHL 8.
However, I would not expect people to be running RHL 7.x or 8.x on
mainframes, but rather RHLES variants. The principle holds though,
expect compatibility libraries to be available to run binaries on more
recent releases than they were built on.
Something more likely to trip you up (but they are relatively minor) are
the initialisation scripts and the like. Red Hat and Debian
initialisation scripts and configuration files are quite different.
Also, Debian uses a different (better?) packaging system from Red Hat
and SuSE. There is a utility to convert, but my own preference is to
build for all target systems so as to ensure there cannot be significant
discrepancies with libraries, packaging etc .
> There are things you can do to improve that, like not using exceptions.
>
> Peter
>
--
Cheers
John.
Join the "Linux Support by Small Businesses" list at
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Copyright John Summerfield. Reproduction prohibited.
