public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: gafton@redhat.com
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: the setrlimit changes in glibc 2.1.3
Date: Thu, 13 Jan 2000 06:18:00 -0000	[thread overview]
Message-ID: <200001131418.PAA00754@delius.kettenis.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10001130836420.14119-100000@localhost.localdomain>

   Date: Thu, 13 Jan 2000 08:38:32 -0500 (EST)
   From: Cristian Gafton <gafton@redhat.com>

   On Thu, 13 Jan 2000, Andreas Schwab wrote:

   > Then you must rebuild the shared lib in question.  Binary compatibility is
   > only about *runtime* compatibility, but not *linktime* compatibility.

   No way. I don't see why I should do that.

Because mixing modules that use interfaces that are binary
incompatible is dangerous.  In the case of setrlimit, the rlim_t type
changed.  If both the shared library and an application that links
with that library use rlim_t in their communication, bad things may
happen if the library is using the old type and the application is
using the new type.

By the way, you should not simply rebuild the shared lib, but also
check if the interfaces it provides didn't change because of the
changes to the interface in libc.  If the interfaces did change, you
must bump the lib's soname or version the symbols in your library
itself.

Mark

  reply	other threads:[~2000-01-13  6:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200001122306.PAA02712@localhost.cygnus.com>
2000-01-12 15:12 ` Cristian Gafton
2000-01-13  4:32   ` Andreas Schwab
2000-01-13  5:38     ` Cristian Gafton
2000-01-13  6:18       ` Mark Kettenis [this message]
2000-01-13  6:35         ` Cristian Gafton
2000-01-13  6:55           ` Jakub Jelinek
2000-01-13  7:02           ` Mark Kettenis
2000-01-13 11:40             ` Roland McGrath
2000-01-13 12:45               ` Joel Klecker
2000-01-13 14:47               ` Thorsten Kukuk
2000-01-13 15:20                 ` glibc release management Roland McGrath
2000-01-13 15:34                   ` Thorsten Kukuk
2000-01-13 23:13                   ` Cristian Gafton
2000-01-14  0:46                     ` Thorsten Kukuk
     [not found]                       ` <200001141946.LAA00505@localhost.cygnus.com>
2000-01-14 13:10                         ` Thorsten Kukuk
2000-01-14  1:05               ` the setrlimit changes in glibc 2.1.3 Andreas Jaeger
2000-01-14 13:20                 ` Roland McGrath
     [not found] <200001122329.PAA02745@localhost.cygnus.com>
2000-01-12 15:41 ` Cristian Gafton
2000-01-12 20:41   ` H . J . Lu
2000-01-12 22:21     ` Thorsten Kukuk
2000-01-13  6:33       ` Mark Kettenis
2000-01-13  9:26       ` H . J . Lu
2000-01-12 12:30 Cristian Gafton
2000-01-12 14:58 ` Mark Kettenis
2000-01-12 15:44   ` Cristian Gafton
2000-01-12 20:21     ` H . J . Lu

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=200001131418.PAA00754@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=gafton@redhat.com \
    --cc=libc-hacker@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).