[8562] in linux-scsi channel archive
OT: glibc2.1 bin compat. [was: SCSI_IOCTL_GET_IDLUN changes in lk 2.3/2.4]
daemon@ATHENA.MIT.EDU (Kurt Garloff)
Fri Apr 7 07:49:01 2000
Date: Fri, 7 Apr 2000 13:42:07 +0200
From: Kurt Garloff <garloff@suse.de>
To: Joerg Schilling <schilling@fokus.gmd.de>
Cc: linux-scsi@vger.rutgers.edu
Message-ID: <20000407134207.G13447@mobil.tue.nl>
Mail-Followup-To: Joerg Schilling <schilling@fokus.gmd.de>,
linux-scsi@vger.rutgers.edu
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="9/eUdp+dLtKXvemk"
In-Reply-To: <200004050726.JAA06383@fokus.gmd.de>; from schilling@fokus.gmd.de on Wed, Apr 05, 2000 at 09:26:42AM +0200
--9/eUdp+dLtKXvemk
Content-Type: text/plain; charset=us-ascii
On Wed, Apr 05, 2000 at 09:26:42AM +0200, Joerg Schilling wrote:
> BTW: libc.so.6 is still not usable for applications that ship
> in binary form: RedHat and SuSE use binary incompatible libraries
> both called libc.so.6
>
> There is a high demand to force ReaHat and SuSE to talk together
> and fix this. As libc.so.6 is burned out for this reason, there
> should be a libc.so.7 that may be used again for binary distributions.
Joerg,
In glibc binary compatibility is not defined by the soname (which is
libc.so.6 no matter how the actual file is named), but by the internal
symbol versions. In theory a given symbol like fopen@GLIBC_2_1_2 is supposed
to be compatible between Caldera/SuSE/RedHat/Debian/... libc 2.1.x. There is
no explicit testing of this though, it would be rather hard to do too
because the differences can be subtly and maybe often break only some apps.
Changing symbol versions for every small bugfix would be silly too and
quickly cause a big mess.
Often incompatibilities are caused by other things too, like gcc libgcc1/2
binary problems etc.
As you can see, a glibc _up_grade should never break binaries. A downgrade of
course can always cause problems ...
If you compile your binaries / shlibs with glibc-2.1.2, it should work on
all distros using 2.1.2 or later. If not, it's a bug either in glibc or your
code. Don't hesitate to report it to the glibc folks and discuss it.
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
--9/eUdp+dLtKXvemk
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1c- (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE47cmOxmLh6hyYd04RAegjAKC2jLPb9S6lGPATO22B2M/vHpDuzACfdwtl
bHbNj4L92IsIBMg6lRTfn4E=
=bTkj
-----END PGP SIGNATURE-----
--9/eUdp+dLtKXvemk--
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
