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 /manual/install.texi | |
| 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 'manual/install.texi')
| -rw-r--r-- | manual/install.texi | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/manual/install.texi b/manual/install.texi index cf3023b..5ac0e78 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -222,11 +222,11 @@ from underneath. 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 |