about summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@gmail.com>2012-01-07 11:29:31 -0500
committerUlrich Drepper <drepper@gmail.com>2012-01-07 11:29:31 -0500
commitbdeba1354b7364d9b7857a048286a71ddbcdff86 (patch)
tree0693046c0fed2fe835c83814bd7f98a5075bc920 /FAQ.in
parentd75a0a62b12c35ee85f786d5f8d155ab39909411 (diff)
downloadglibc-bdeba1354b7364d9b7857a048286a71ddbcdff86.tar.gz
glibc-bdeba1354b7364d9b7857a048286a71ddbcdff86.tar.xz
glibc-bdeba1354b7364d9b7857a048286a71ddbcdff86.zip
Remove --enable-omitfp support
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in16
1 files changed, 1 insertions, 15 deletions
diff --git a/FAQ.in b/FAQ.in
index af61599a70..216155c763 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -265,21 +265,7 @@ any other link path.
 
 ??	What's the problem with configure --enable-omitfp?
 
-{AJ} When --enable-omitfp is set the libraries are built without frame
-pointers.  Some compilers produce buggy code for this model and therefore we
-don't advise using it at the moment.
-
-If you use --enable-omitfp, you're on your own.  If you encounter problems
-with a library that was build this way, we advise you to rebuild the library
-without --enable-omitfp.  If the problem vanishes consider tracking the
-problem down and report it as compiler failure.
-
-Since a library built with --enable-omitfp is undebuggable on most systems,
-debuggable libraries are also built - you can use them by appending "_g" to
-the library names.
-
-The compilation of these extra libraries and the compiler optimizations slow
-down the build process and need more disk space.
+{} Removed.  Does not apply anymore.
 
 ??	I get failures during `make check'.  What should I do?