Marat Radchenko <ma...@slonopotamus.org> writes:
> When crosscompiling, one cannot rely on `uname` from host system.
That may well be true, but is that limited to cross-compiling to
mingw? Would it be generally true for any cross compilation,
wouldn't it?
What I am wondering is if it is a better solution to make it easier
to allow somebody who is cross compiling to express "Mr. Makefile,
we know better than you and want you to do a MINGW build for us
without checking with `uname -?` yourself", i.e.
$ make uname_O=MINGW uname_S=MINGW
which would hopefully allow cross-compilation into other
environments, not just MINGW.
>
> Signed-off-by: Marat Radchenko <ma...@slonopotamus.org>
> ---
> config.mak.uname | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/config.mak.uname b/config.mak.uname
> index 9f7037e..182da50 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -14,6 +14,11 @@ ifdef MSVC
> uname_O := Windows
> endif
>
> +ifneq (,$(findstring mingw,$(CC_MACH)))
> + uname_S := MINGW
> + uname_O := MINGW
> +endif
> +
> # We choose to avoid "if .. else if .. else .. endif endif"
> # because maintaining the nesting to match is a pain. If
> # we had "elif" things would have been much nicer...
> --
> 2.1.1
>
> --
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
