From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: Configure tweak for _mktemp()
Date: Wed, 8 Mar 2000 07:37:52 +0000 [thread overview]
Message-ID: <1000308073752.ZM8603@candle.brasslantern.com> (raw)
Dan Nelson wrote:
} Under FreeBSD, you can use the undocumented _mktemp() function to
} bypass the linker warning. I don't know if the other BSDs implement
} their warning message in the same way. Does OpenBSD print a similar
} warning for sprintf? :)
}
} char * _mktemp(char *path)
} { return(_gettemp(path, (int *)NULL, 0, 0) ? path : (char *)NULL);
} }
Index: configure.in
===================================================================
RCS file: /extra/cvsroot/zsh/zsh-3.1/configure.in,v
retrieving revision 1.69
diff -u -r1.69 configure.in
--- configure.in 2000/02/28 04:44:47 1.69
+++ configure.in 2000/03/08 06:34:23
@@ -813,7 +813,7 @@
nis_list initgroups fchdir cap_get_proc readlink nice \
getgrgid getgrnam getpwent getpwnam getpwuid setpgrp \
inet_aton inet_pton inet_ntop getipnodebyname gethostbyname2 \
- fseeko ftello mmap munmap msync ftruncate setlocale)
+ fseeko ftello mmap munmap msync ftruncate setlocale _mktemp)
dnl ---------------
dnl CHECK FUNCTIONS
Index: Src/utils.c
===================================================================
@@ -1091,7 +1091,12 @@
if (!(s = getsparam("TMPPREFIX")))
s = DEFAULT_TMPPREFIX;
+#ifdef HAVE__MKTEMP
+ /* Zsh uses mktemp() safely, so silence the warnings */
+ return ((char *) _mktemp(dyncat(unmeta(s), "XXXXXX")));
+#else
return ((char *) mktemp(dyncat(unmeta(s), "XXXXXX")));
+#endif
}
/* Check if a string contains a token */
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
reply other threads:[~2000-03-08 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000308073752.ZM8603@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).