From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH] newlib: posix: use local includes for local headers
Date: Wed, 16 Feb 2022 23:51:52 -0500 [thread overview]
Message-ID: <20220217045152.14255-1-vapier@gentoo.org> (raw)
These headers aren't installed, so use "" includes instead of <> so
we don't search system header paths. This matches the style used
elsewhere in the tree for these local headers, and makes it work
w/out explicit -I flags (as needed with non-recursive make).
---
newlib/libc/posix/collate.c | 4 ++--
newlib/libc/posix/rune.h | 2 +-
newlib/libc/time/gettzinfo.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/newlib/libc/posix/collate.c b/newlib/libc/posix/collate.c
index 8bb04ef0d088..a2f62c978f93 100644
--- a/newlib/libc/posix/collate.c
+++ b/newlib/libc/posix/collate.c
@@ -28,13 +28,13 @@
#include <sys/cdefs.h>
#include "namespace.h"
-#include <rune.h>
+#include "rune.h"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <unistd.h>
-#include <sysexits.h>
+#include "sysexits.h"
#include "un-namespace.h"
#include "collate.h"
diff --git a/newlib/libc/posix/rune.h b/newlib/libc/posix/rune.h
index 6966d33750be..888e6fb0423b 100644
--- a/newlib/libc/posix/rune.h
+++ b/newlib/libc/posix/rune.h
@@ -36,7 +36,7 @@
#ifndef _RUNE_H_
#define _RUNE_H_
-#include <runetype.h>
+#include "runetype.h"
#include <stdio.h>
#define _PATH_LOCALE "/usr/share/locale"
diff --git a/newlib/libc/time/gettzinfo.c b/newlib/libc/time/gettzinfo.c
index 54c9bc2f0af7..c28e72f0a858 100644
--- a/newlib/libc/time/gettzinfo.c
+++ b/newlib/libc/time/gettzinfo.c
@@ -1,5 +1,5 @@
#include <sys/types.h>
-#include <local.h>
+#include "local.h"
/* Shared timezone information for libc/time functions. */
static __tzinfo_type tzinfo = {1, 0,
--
2.34.1
next reply other threads:[~2022-02-17 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 4:51 Mike Frysinger [this message]
2022-02-18 10:00 ` Corinna Vinschen
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=20220217045152.14255-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).