From: Pavel Fedin <p.fedin@samsung.com>
To: linux-kernel@vger.kernel.org
Cc: "'Yaakov Selkowitz'" <yselkowitz@cygwin.com>
Subject: PING: [PATCH] Avoid conflict with host definitions when cross-compiling
Date: Wed, 17 Jun 2015 11:34:48 +0300 [thread overview]
Message-ID: <00f601d0a8d8$79242a80$6b6c7f80$@samsung.com> (raw)
PING!
2 Yaakov: Hello! I remember you upstreamed this one:
https://cygwin.com/ml/cygwin/2012-06/msg00221/0002-tools-include-use-stdint-types-for-user
-space-bytesh.patch
Who is the person to cc: ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org] On
> Behalf Of Pavel Fedin
> Sent: Wednesday, June 03, 2015 11:25 AM
> To: linux-kernel@vger.kernel.org
> Subject: [PATCH] Avoid conflict with host definitions when cross-compiling
>
> 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.
>
> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
> ---
> 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/
reply other threads:[~2015-06-17 8:35 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='00f601d0a8d8$79242a80$6b6c7f80$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yselkowitz@cygwin.com \
/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
all inboxes | Powered by JetHome®