+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].
+
1999-03-08 Ulrich Drepper <drepper@cygnus.com>
* manual/signal.texi (Termination in Handler): Correct example.
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
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
If you are upgrading from a previous installation of glibc 2.0 or 2.1,
@samp{make install} will do the entire job. If you're upgrading from
Linux libc5 or some other C library, you need to rename the old
-@file{/usr/include} directory out of the way first, or you will end up
-with a mixture of header files from both libraries, and you won't be
-able to compile anything. You may also need to reconfigure GCC to work
-with the new library. The easiest way to do that is to figure out the
-compiler switches to make it work again
+@file{/usr/include} directory out of the way before running @samp{make
+install}, or you will end up with a mixture of header files from both
+libraries, and you won't be able to compile anything. You may also need
+to reconfigure GCC to work with the new library. The easiest way to do
+that is to figure out the compiler switches to make it work again
(@samp{-Wl,-dynamic-linker=/lib/ld-linux.so.2} should work on Linux
systems) and use them to recompile gcc. You can also edit the specs
file (@file{/usr/lib/gcc-lib/@var{TARGET}/@var{VERSION}/specs}), but
compatibility.
@end deftypevr
+The remaining operating modes are BSD extensions. They exist only
+on some systems. On other systems, these macros are not defined.
+
@comment fcntl.h
@comment BSD
@deftypevr Macro int O_SHLOCK