docs/163119: mktemp(3) is referring to (now) non-existent gcc option

[Yuri Pankov]

>Number:         163119
>Category:       docs
>Synopsis:       mktemp(3) is referring to (now) non-existent gcc option
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 08 08:50:11 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Yuri Pankov
>Release:        FreeBSD 9.0-RC2 amd64
>Organization:
Nexenta Systems, Inc.
>Environment:
System: FreeBSD procyon.xvoid.org 9.0-RC2 FreeBSD 9.0-RC2 #0 r228164: Thu Dec 1 08:32:46 MSK 2011 yuri at procyon.xvoid.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
mktemp(3) is presumably referring to gcc's -fwritable-strings, which doesn't exist in recent releases (and it's a bad advice anyway).
>How-To-Repeat:
>Fix:
--- mktemp.3.diff begins here ---
Index: lib/libc/stdio/mktemp.3
===================================================================
--- lib/libc/stdio/mktemp.3	(revision 228346)
+++ lib/libc/stdio/mktemp.3	(working copy)
@@ -180,12 +180,6 @@
 will result in a core dump due to
 .Fn mkstemp
 attempting to modify the string constant that was given.
-If the program in question makes heavy use of that type
-of function call, you do have the option of compiling the program
-so that it will store string constants in a writable segment of memory.
-See
-.Xr gcc 1
-for more information.
 .Sh SEE ALSO
 .Xr chmod 2 ,
 .Xr getpid 2 ,
--- mktemp.3.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: