From: Valentin Ochs <a@0au.de>
Cc: trivial@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] fixdep: define _POSIX_C_SOURCE
Date: Sat, 9 Apr 2011 22:55:32 +0200 [thread overview]
Message-ID: <20110409205532.GE4663@erwin> (raw)
fixdep.c uses PATH_MAX without defining the required _POSIX_C_SOURCE
feature test macro. This prevents compilation with the musl libc.
The patch applies to 2.6.38.2.
Best regards,
Valentin
Signed-off-by: Valentin Ochs <a@0au.de>
---
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -102,6 +102,7 @@
* through arch/um/include/uml-config.h; this fixdep "bug" makes sure that
* those files will have correct dependencies.
*/
+#define _POSIX_C_SOURCE 200809L
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/mman.h>
WARNING: multiple messages have this Message-ID (diff)
From: Valentin Ochs <a@0au.de>
To: unlisted-recipients:; (no To-header on input)
Cc: trivial@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] fixdep: define _POSIX_C_SOURCE
Date: Sat, 9 Apr 2011 22:55:32 +0200 [thread overview]
Message-ID: <20110409205532.GE4663@erwin> (raw)
fixdep.c uses PATH_MAX without defining the required _POSIX_C_SOURCE
feature test macro. This prevents compilation with the musl libc.
The patch applies to 2.6.38.2.
Best regards,
Valentin
Signed-off-by: Valentin Ochs <a@0au.de>
---
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -102,6 +102,7 @@
* through arch/um/include/uml-config.h; this fixdep "bug" makes sure that
* those files will have correct dependencies.
*/
+#define _POSIX_C_SOURCE 200809L
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/mman.h>
next reply other threads:[~2011-04-09 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 20:55 Valentin Ochs [this message]
2011-04-09 20:55 ` [PATCH] fixdep: define _POSIX_C_SOURCE Valentin Ochs
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=20110409205532.GE4663@erwin \
--to=a@0au.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.