This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Date: Wed, 12 Jan 2000 15:30:25 -0500 (EST) From: Cristian Gafton <gafton@redhat.com> The current changes in setrlimit that were backported to glibc 2.1.3 are causing this library to become once again binary incompatible with the preivious releases. You you have any dynamic library linked against a previous version of glibc that is calling setrlimit, you'll not be able to use it after upgrading to glibc 2.1.3. Of course we are no longer binary compatible. We have fixed some bugs :). But seriously: At linking stage, the linker complains about an undefined setrlimit@@GLIBC_2.0 symbol - this is because previously the setrlimit was not a versioned symbol. If this is really what is happening, that is: * You built a shared library, that references setrlimit, linked against glibc 2.1, 2.1.1 or 2.1.2. * You replaced glibc with version 2.1.3. * If you now link against your shared library you get a warning about setrlimit@@GLIBC_2.0 undefined. Then either something went wrong during your built of glibc 2.1.3, or there is a bug in the (static) linker. To check what is really you could do nm /lib/libc-2.1.3.so | grep setrlimit This should output at least two lines looking like xxxxxxxx T setrlimit@@GLIBC_2.1.3 xxxxxxxx T setrlimit@GLIBC_2.0 If this is not the case, something went wrong when buildig glibc 2.1.3. Otherwise it is most likely a linker bug. Mark
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |