Provide a hook to make __sF visible outside of libc for commercial apps

if WANT_COMPAT4_STDIO is defined when compiling libc.

Submitted by: Steve Kargl <sgk@troutmask.apl.washington.edu>

2 files changed, 16 insertions, 0 deletions

diff --git a/share/examples/etc/make.conf b/share/examples/etc/make.conf
index a0d269e..1aa2f78 100644
--- a/share/examples/etc/make.conf
+++ b/share/examples/etc/make.conf
@@ -171,6 +171,14 @@
 #COMPAT3X=	yes
 #COMPAT4X=	yes
 #
+# If you have a commercial application for a FreeBSD 4.x that cannot easily
+# be updated to a FreeBSD 5.x application and it generates the error message
+# "undefined reference to `__sF'", then you can uncomment the following
+# line to build a libc compatibility with FreeBSD 4.x.  NOTE, THIS SHOULD BE
+# USED AS A LAST RESORT.
+#
+#WANT_COMPAT4_STDIO=	yes
+#
 #
 # Default format for system documentation, depends on your printer.
 # Set this to "ascii" for simple printers or screen
diff --git a/share/man/man5/make.conf.5 b/share/man/man5/make.conf.5
index 0d6c745..0a810c5 100644
--- a/share/man/man5/make.conf.5
+++ b/share/man/man5/make.conf.5
@@ -605,6 +605,14 @@ levels to a lower one.
 and above is known to trigger known optimizer bugs at various
 times \(em this is worse on the Alpha platform.
 The value assigned is the highest optimization value used.
+.It Va WANT_COMPAT4_STDIO
+.Pq Vt bool
+If you have a commercial application for a FreeBSD 4.x that cannot easily
+be updated to a FreeBSD 5.x application and it generates the error message
+.Dq undefined reference to `__sF' ,
+then you can uncomment the following line to build a libc compatibility with
+FreeBSD 4.x.
+.Em NOTE, THIS SHOULD BE USED AS A LAST RESORT.
 .El
 .Pp
 The following list provides a name and short description for variables