diff options
author | Ulrich Drepper <drepper@redhat.com> | 1999-01-21 14:17:43 +0000 |
---|---|---|
committer | Ulrich Drepper <drepper@redhat.com> | 1999-01-21 14:17:43 +0000 |
commit | 50b65db1ee9a87be6ead950e7cffa4c223e689fd (patch) | |
tree | 28ecfe4141d27f096b12cd3174bbbd5c0b9c3d79 /FAQ.in | |
parent | 1d28e93cabf235de32a594d7b770551a34be0e75 (diff) | |
download | glibc-50b65db1ee9a87be6ead950e7cffa4c223e689fd.zip glibc-50b65db1ee9a87be6ead950e7cffa4c223e689fd.tar.gz glibc-50b65db1ee9a87be6ead950e7cffa4c223e689fd.tar.bz2 |
Update.
1999-01-21 Ulrich Drepper <drepper@cygnus.com>
* elf/dl-close.c: Rewrite the way adding to the global scope works
to handle error cases better than the last change.
The l_global flag is now only set when the object is actually
counted in the global scope list.
* elf/dl-deps.c: Likewise.
* elf/dl-open.c: Likewise.
Diffstat (limited to 'FAQ.in')
-rw-r--r-- | FAQ.in | 20 |
1 files changed, 10 insertions, 10 deletions
@@ -849,16 +849,16 @@ Another problem is that older binaries that were linked statically against glibc 2.0 will reference the older nss modules (libnss_files.so.1 instead of libnss_files.so.2), so don't remove them. Also, the old glibc-2.0 compiled static libraries (libfoo.a) which happen to depend on the older libio -behavior will be broken by the glibc 2.1 upgrade. The idea is to produce a -libcompat.a that people will be able to use to link in if they want to -compile a static library generated against glibc 2.0 into a program on a -glibc 2.1 system. You should just add -lcompat and you should be fine. - -The glibc-compat add-on will provide the libnss_* files and other stuff so -that it is possible to use static library compiled against glibc 2.0 for -development on a glibc 2.1 based system. Please note that this is currently -just an experiment, although the nss modules part should work. - +behavior will be broken by the glibc 2.1 upgrade. We plan to produce a +compatibility library that people will be able to link in if they want +to compile a static library generated against glibc 2.0 into a program +on a glibc 2.1 system. You just add -lcompat and you should be fine. + +The glibc-compat add-on will provide the libcompat.a library, the older +nss modules, and a few other files. Together, they should make it +possible to do development with old static libraries on a glibc 2.1 +system. This add-on is still in development. You can get it from <URL> +but please keep in mind that it is experimental. ? Source and binary incompatibilities, and what to do about them |