Al,
I found that files and libraries located in different directories (in
comparison to RedHat) to be the main problem when building under Debian.
Going back in time with glibc (Debian) probably is not going to be much of a
problem. Only when a glibc is introduced which is newer than in any other
distribution (RedHat 9) will it become a problem. Most distributions catch
up quickly (except Debian).
Steve.
-----Original Message-----
From: Alasdair Allan [mailto:[log in to unmask]]
Sent: 03 November 2003 14:39
To: [log in to unmask]
Subject: Re: The future of RedHat
> Just how different are these various Linux flavours and their compilere?
Not much, the main difference is when they all move to new flavours of
gcc/glibc, they rarely do so "in sync" as it were. So if our "prefered
platform" moved went to a non-backwards compatible glibc version, and
nobody else did (RH has done this at least once!), then our software
isn't binary compatible (must be built from source) for all the
other distributions.
Of course when Starlink Classic is in CVS amd builds using ./configure
then this isn't going to be a problem. This is what GNU Configure is
designed to deal with automatically...
Al.
|