the setrlimit changes in glibc 2.1.3
Andreas Schwab
schwab@suse.de
Thu Jan 13 04:32:00 GMT 2000
Cristian Gafton <gafton@redhat.com> writes:
|> On Wed, 12 Jan 2000, Geoff Keating wrote:
|>
|> > If you run 'nm libc.so.6 | grep setrlimit', do you get
|> >
|> > 000b18b4 T setrlimit@@GLIBC_2.1.3
|> > 000b1b74 T setrlimit@GLIBC_2.0
|> >
|> > (of course, your hex numbers will vary)?
|>
|> The problem is that the linker complains about a missing
|> setrlimit@@GLIBC_2.0 (note the double @@), which means that the shared lib
|> in question has a reference to an unversioned setrlimit.
Then you must rebuild the shared lib in question. Binary compatibility is
only about *runtime* compatibility, but not *linktime* compatibility.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
More information about the Libc-hacker
mailing list