From: Michal Marek <mmarek@suse.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling
Date: Fri, 21 Aug 2015 14:49:32 +0200 [thread overview]
Message-ID: <55D71E5C.2080807@suse.com> (raw)
In-Reply-To: <019301d0db4a$a60a7370$f21f5a50$@samsung.com>
On 2015-08-20 15:18, Pavel Fedin wrote:
> Hi!
>
>> If you already have the patches, it won't hurt to send them.
>
> I have one of them, need to make more.
>
>> Although I
>> was under the impression that the .exe suffix is somehow automagically
>> handled by Cygwin..?
>
> In 99% of cases - yes. But at least there is a problem with implicit rules in GNU Make.
That sounds good. I feared we would have to write scripts/foo$(EXE)
everywhere.
> Actually, here i am talking about patch 0002 from this set:
> https://www.cygwin.com/ml/cygwin/2012-06/msg00221.html.
Patch 0002 has been merged in the meantime.
> This HOWTO was created when the kernel was
> really old, and now some more tools face a similar problem, like certificate generator for security
> subsystem. I will check this.
OK.
Michal
next prev parent reply other threads:[~2015-08-21 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 10:52 [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling Pavel Fedin
2015-08-20 11:31 ` Michal Marek
2015-08-20 12:31 ` Pavel Fedin
2015-08-20 12:38 ` Michal Marek
2015-08-20 13:18 ` Pavel Fedin
2015-08-21 12:49 ` Michal Marek [this message]
2015-08-24 6:44 ` Pavel Fedin
2015-08-24 16:36 ` Masahiro Yamada
2015-08-25 7:47 ` Pavel Fedin
2015-08-25 8:18 ` Masahiro Yamada
2015-08-25 9:27 ` Pavel Fedin
2015-08-25 9:56 ` Michal Marek
2015-08-25 9:59 ` Pavel Fedin
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=55D71E5C.2080807@suse.com \
--to=mmarek@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=p.fedin@samsung.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 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.