public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: forestalling GNU incompatibility - proposal for binary relative dynamic linking
Date: Tue, 25 Jan 2005 10:25:29 +0100	[thread overview]
Message-ID: <200501251025.29624@fortytwo.ch> (raw)
In-Reply-To: <20050124222449.GB16078@venus>

[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]

On Monday 24 January 2005 23.24, Edward Peschko wrote:
[ Linux interoperability in danger - libc != libc ]

Hi,

[this may be just ignorance - I only use one distro (Debian), and don't try 
to mix binaries]

Before discussing solutions: Is there a survey on how bad the problem really 
is?  IIRC some minor API changes were done between some gcc versions, but 
mostly on the C++ side.  I know Debian, too, ships with a quite heavily 
patched toolchain, but the Debian libc/binutils/gcc packagers work together 
with the upstream developers, and many Debian specific patches end up in 
the official releases sooner or later. (And most of Debian's patches 
concern architectures like ARM, m68k, HPPA etc., which the big 
distributions don't support anyway.)

So, I guess, the survey would need to compare only C programs (not C++), 
since you explicitly are talking about libc - C++ has always been more 
difficult.  And, it would be important to differentiate between 
incompatibilites caused by gcc versions from incompatibilities really 
caused by vendor specific modifications.

cheers
-- vbi

P.S.: looking at Debian's libc6 glibc package (2.3.2.ds1-20):
 - 106 patches total
Going by the name of the patch files only:
 - 8 hurd specific
 - 4 arm specific
 - 9 hppa specific
 - 4 m68k specific
 - 3 alpha specific
 - 1 amd64 specific
 - 1 x86 specific
 - 4 sparc specific
 - 5 mips specific
 - 3 ppc specific
 - 1 ia64 specific
 - 3 s390 specific
 - 4 correcting paths/build system only (wouldn't affect the libc API as 
such)
 - 15 locale specific (dito)

So, over half of the patches will likely not affect 95% of Linux users.  Of 
the rest, a good number clearly affect multithreaded programs only (which, 
admittedly, are much more widespread now than a few years back.)  I didn't 
look at any patches at all, so I can't judge how much the patches do really 
change the libc.  Also, I can't say how intrusive the patches of other 
distributions are.

-- 
We are not loved by our friends for what we are; rather, we are loved in
spite of what we are.
  -- Victor Hugo

[-- Attachment #2: Type: application/pgp-signature, Size: 388 bytes --]

      parent reply	other threads:[~2005-01-25  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 22:24 forestalling GNU incompatibility - proposal for binary relative dynamic linking Edward Peschko
2005-01-24 22:47 ` Edward Peschko
2005-01-24 23:08 ` Mike Frysinger
2005-01-24 23:12   ` Edward Peschko
2005-01-24 23:10 ` Richard Henderson
2005-01-24 23:16   ` Edward Peschko
2005-01-24 23:38     ` Richard Henderson
2005-01-24 23:53       ` Edward Peschko
2005-01-25  0:29         ` Daniel Jacobowitz
2005-01-25  9:25 ` Adrian von Bidder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501251025.29624@fortytwo.ch \
    --to=avbidder@fortytwo.ch \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox