From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: 9front@9front.org
Subject: [9front] Re: ape/mkstemp: Set define (was: Include <bsd.h>)
Date: Fri, 07 Jan 2022 15:46:32 +0100 [thread overview]
Message-ID: <87wnjbzjqv.fsf@turtle-trading.net> (raw)
In-Reply-To: <87y23v2shn.fsf@turtle-trading.net> (Benjamin Riefenstahl's message of "Tue, 04 Jan 2022 20:47:16 +0100")
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
Hi all,
The recent commit 1a90e04c0 "ape: export mktemp() in <stdlib.h> when
_BSD_SOURCE is set" reduces the need here to setting that define.
Thanks, benny
[-- Attachment #2.1: Type: text/plain, Size: 272 bytes --]
from postmaster@4ess:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/x-diff
Content-Disposition: inline; filename=mkstemp.patch
[-- Attachment #2.2: mkstemp.patch.suspect --]
[-- Type: application/octet-stream, Size: 511 bytes --]
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Date: Fri, 10 Dec 2021 20:47:09 +0000
Subject: [PATCH] ape/mkstemp: set define for mktemp prototype
---
diff 70edb7fbae4f0a38593c0dc1f936838adc6861ac 45a0f394b723a53a1c5d5b0e266342e0c38a8643
--- a/sys/src/ape/lib/ap/gen/mkstemp.c Fri Jan 7 02:43:52 2022
+++ b/sys/src/ape/lib/ap/gen/mkstemp.c Fri Dec 10 21:47:09 2021
@@ -1,3 +1,4 @@
+#define _BSD_SOURCE 1 /* make mktemp visible */
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
prev parent reply other threads:[~2022-01-07 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 19:47 [9front] ape/mkstemp: Include <bsd.h> Benjamin Riefenstahl
2022-01-07 14:46 ` Benjamin Riefenstahl [this message]
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=87wnjbzjqv.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=9front@9front.org \
/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.
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).