From: Valentin Ochs <a@0au.de>
Cc: Michal Marek <mmarek@suse.cz>,
Roman Zippel <zippel@linux-m68k.org>,
trivial@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] kconfig/kbuild: define _POSIX_C_SOURCE
Date: Sun, 10 Apr 2011 04:09:23 +0200 [thread overview]
Message-ID: <20110410020923.GI4663@erwin> (raw)
The three patched files use 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.
Changes since v1:
- fix scripts/kconfig/lex.zconf.c_shipped
- fix scripts/kconfig/mconf.c
Sorry about the incomplete patch I sent a few hours ago, it won't happen
again. :)
Best regards,
Valentin
Signed-off-by: Valentin Ochs <a@0au.de>
---
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -102,7 +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>
--- a/scripts/kconfig/lex.zconf.c_shipped
+++ b/scripts/kconfig/lex.zconf.c_shipped
@@ -35,6 +35,7 @@
/* First, we deal with platform-specific or compiler-specific issues. */
/* begin standard C headers. */
+#define _POSIX_C_SOURCE 200809L
#include <stdio.h>
#include <string.h>
#include <errno.h>
--- a/scripts/kconfig/mconf.c
+++ b/scripts/kconfig/mconf.c
@@ -7,7 +7,7 @@
*
* i18n, 2005, Arnaldo Carvalho de Melo <acme@conectiva.com.br>
*/
+#define _POSIX_C_SOURCE 200809L
#include <ctype.h>
#include <errno.h>
#include <fcntl.h>
next reply other threads:[~2011-04-10 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 2:09 Valentin Ochs [this message]
2011-04-10 3:34 ` [PATCH v2] kconfig/kbuild: define _POSIX_C_SOURCE Arnaud Lacombe
2011-04-10 14:31 ` Valentin Ochs
2011-04-19 9:54 ` Michal Marek
2011-04-19 17:03 ` Arnaud Lacombe
2011-04-19 17:07 ` Arnaud Lacombe
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=20110410020923.GI4663@erwin \
--to=a@0au.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=trivial@kernel.org \
--cc=zippel@linux-m68k.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