diff options
| author | Ulrich Drepper <drepper@redhat.com> | 1999-03-08 14:50:23 +0000 |
|---|---|---|
| committer | Ulrich Drepper <drepper@redhat.com> | 1999-03-08 14:50:23 +0000 |
| commit | 27e309c17790ac7d0a2163785a2f4633f87b4958 (patch) | |
| tree | 26c30351b1d5020802dc71760e41494c61904615 /FAQ.in | |
| parent | 57b4b78a238953382c0e2ef07e969138e96b1f16 (diff) | |
| download | glibc-27e309c17790ac7d0a2163785a2f4633f87b4958.zip glibc-27e309c17790ac7d0a2163785a2f4633f87b4958.tar.gz glibc-27e309c17790ac7d0a2163785a2f4633f87b4958.tar.bz2 | |
Update.
1999-03-05 Andreas Jaeger <aj@arthur.rhein-neckar.de>
* manual/llio.texi (Open-time Flags): Clarify that O_SHLOCK and
O_EXLOCK are BSD extensions.
Reported by Jochen Voss <voss@mathematik.uni-kl.de> [PR libc/985].
Diffstat (limited to 'FAQ.in')
| -rw-r--r-- | FAQ.in | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -395,10 +395,11 @@ prefix to something like /usr/local/glibc2 which is not used for anything.) The dangers when installing glibc in /usr are twofold: * glibc will overwrite the headers in /usr/include. Other C libraries - install a different but overlapping set of headers there, so the - effect will probably be that you can't compile anything. You need to - rename /usr/include out of the way first. (Do not throw it away; you - will then lose the ability to compile programs against your old libc.) + install a different but overlapping set of headers there, so the effect + will probably be that you can't compile anything. You need to rename + /usr/include out of the way before running `make install'. (Do not throw + it away; you will then lose the ability to compile programs against your + old libc.) * None of your old libraries, static or shared, can be used with a different C library major version. For shared libraries this is not a |