From: Pavel Fedin <p.fedin@samsung.com>
To: linux-kbuild@vger.kernel.org
Cc: 'Jiri Kosina' <jkosina@suse.cz>, trivial@kernel.org
Subject: [RESEND-3 PATCH trivial] Avoid conflict with host definitions when cross-compiling
Date: Wed, 15 Jul 2015 11:41:42 +0300 [thread overview]
Message-ID: <00e101d0beda$13637ee0$3a2a7ca0$@samsung.com> (raw)
Certain platforms (e. g. BSD-based ones) define some ELF constants according to host.
This patch fixes problems with cross-building Linux kernel on these platforms (e. g. building ARM
32-bit version on x86-64 host).
Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
---
If you are not fond of mentioning Cygwin in the comment, feel free to change it to "BSD-based" or
whatever else you feel appropriate
---
scripts/mod/modpost.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/mod/modpost.h b/scripts/mod/modpost.h
index 168b43d..9f51365 100644
--- a/scripts/mod/modpost.h
+++ b/scripts/mod/modpost.h
@@ -11,6 +11,12 @@
#include "elfconfig.h"
+/* Cygwin's elf.h defines these according to host's word size */
+#undef ELF_ST_BIND
+#undef ELF_ST_TYPE
+#undef ELF_R_SYM
+#undef ELF_R_TYPE
+
#if KERNEL_ELFCLASS == ELFCLASS32
#define Elf_Ehdr Elf32_Ehdr
--
1.9.5.msysgit.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2015-07-15 8:41 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='00e101d0beda$13637ee0$3a2a7ca0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=jkosina@suse.cz \
--cc=linux-kbuild@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 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).