summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.de>2002-05-19 18:37:21 +0000
committerAndreas Jaeger <aj@suse.de>2002-05-19 18:37:21 +0000
commit79ab8d898d0e16d8394c0203a14db6080d6841b1 (patch)
tree839e1bdafafbe642d8dd911269b16c4514c79f60 /FAQ.in
parentbc9307fc941edf641f2cf1f9cfaa0cc0aaf5e91e (diff)
downloadglibc-79ab8d898d0e16d8394c0203a14db6080d6841b1.tar.gz
glibc-79ab8d898d0e16d8394c0203a14db6080d6841b1.tar.xz
glibc-79ab8d898d0e16d8394c0203a14db6080d6841b1.zip
Warn against installing into /usr/local
2002-05-19  Andreas Jaeger  <aj@suse.de>

	* sysdeps/unix/sysv/linux/configure.in: Warn against an
	installation in /usr/local.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in13
1 files changed, 13 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index f35dd342f6..b6d4ac00c5 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1028,6 +1028,19 @@ This version is needed because the fpos_t type and a few libio internals
 have changed in glibc 2.2, and gcc 2.95.3 contains a corresponding patch.
 
 
+??	Why shall glibc never get installed on GNU/Linux systems in
+/usr/local?
+
+{AJ} The GNU C compiler treats /usr/local/include and /usr/local/lib in a
+special way, these directories will be searched before the system
+directories.  Since on GNU/Linux the system directories /usr/include and
+/usr/lib contain a --- possibly different --- version of glibc and mixing
+certain files from different glibc installations is not supported and will
+break, you risk breaking your complete system.  If you want to test a glibc
+installation, use another directory as argument to --prefix.  If you like to
+install this glibc version as default version, overriding the existing one,
+use --prefix=/usr and everything will go in the right places.
+
 ? Source and binary incompatibilities, and what to do about them
 
 ??	I expect GNU libc to be 100% source code compatible with