From: Michal Marek <mmarek@suse.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Pavel Fedin <p.fedin@samsung.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH TRIVIAL v2] Avoid conflict with host definitions when cross-compiling
Date: Tue, 25 Aug 2015 11:56:51 +0200 [thread overview]
Message-ID: <55DC3BE3.6010207@suse.com> (raw)
In-Reply-To: <CAK7LNAQ31nrSZ9vjVGa3p_rr85E0V6xZSaA3xKt3JxYAMMtnLg@mail.gmail.com>
On 2015-08-25 10:18, Masahiro Yamada wrote:
> 2015-08-25 16:47 GMT+09:00 Pavel Fedin <p.fedin@samsung.com>:
>> Hello!
>>
>>> I am not happy with getting weird code to work around issues on
>>> non-Linux systems.
>>
>> What is your criteria of being weird? Why are four #undef's weird ?
>
>
> I am not criticizing your particular patch.
>
> Once we decide to support building on other OSes,
> I fear more and more patches would come in
> to fix building issues.
While nowadays Linux is often the first OS ported to a new architecture
and is cross compiled on another Linux system, I think portable code is
a virtue on its own, _unless_ it requires having compatibility wrappers
for half of the library calls and whatnot. It's hard to draw a line, but
it'd say patches to enable build on Cygwin are OK (since it emulates a
POSIX system quite well), whereas patches to enable build on native
Windows, dealing with pathname lookup differences, .exe suffixes, adding
a libc wrapper, etc, would be frowned upon.
Would you agree to such loosely defined criteria?
Michal
next prev parent reply other threads:[~2015-08-25 9:56 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
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 [this message]
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=55DC3BE3.6010207@suse.com \
--to=mmarek@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=p.fedin@samsung.com \
--cc=yamada.masahiro@socionext.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.