9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: [9front] ape: remove _SUSV2_SOURCE guard from inttypes.h
Date: Sat, 23 Jan 2021 19:09:14 -0800	[thread overview]
Message-ID: <79E6334FEED4A11A90F7C0E5B4BF1C15@arrow.hsd1.ca.comcast.net> (raw)

inttypes.h was added to C99, and this is the only header that used
_SUSV2_SOURCE.

Also, remove now unneeded _SUSV2_SOURCE from python mkfile.

diff -r d920fb7594b8 -r 26db75f8e734 sys/include/ape/inttypes.h
--- a/sys/include/ape/inttypes.h	Sat Jan 23 13:45:08 2021 -0800
+++ b/sys/include/ape/inttypes.h	Sat Jan 23 13:57:23 2021 -0800
@@ -1,7 +1,3 @@
-#ifndef _SUSV2_SOURCE
-#error "inttypes.h is SUSV2"
-#endif
-
 #ifndef _INTTYPES_H_
 #define _INTTYPES_H_ 1
 
diff -r d920fb7594b8 -r 26db75f8e734 sys/src/cmd/python/Extra/mkfile
--- a/sys/src/cmd/python/Extra/mkfile	Sat Jan 23 13:45:08 2021 -0800
+++ b/sys/src/cmd/python/Extra/mkfile	Sat Jan 23 13:57:23 2021 -0800
@@ -7,7 +7,7 @@
 
 </sys/src/cmd/mklib
 
-CFLAGS=-c -I.. -I../Include -DT$objtype -D_SUSV2_SOURCE -DNDEBUG
+CFLAGS=-c -I.. -I../Include -DT$objtype -DNDEBUG
 
 %.$O: %.c
 	$CC $CFLAGS -o $stem.$O $stem.c

                 reply	other threads:[~2021-01-24  6:22 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=79E6334FEED4A11A90F7C0E5B4BF1C15@arrow.hsd1.ca.comcast.net \
    --to=mforney@mforney.org \
    --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).